No, that can be actually not concluded from the trigger section, assuming you are referring to this:
"trigger": {
"triggered_time": null,
"scheduled_time": null,
"previous_scheduled_time": null,
"next_scheduled_time": null
},
The properties here are null because the watch was executed by manual execution. Thus, it has no schedule in this case.
If you want to learn about the status of the automatically triggered watch executions, go to the overview page of Signals and click on the “Execution History” icon on the left side of the watch:
On the following page, you get a list of the statuses of all executions of the watch. Click on an entry to see the detailed information.
However, looking at the watch definition, I just notice that the watch is missing a trigger definition. Triggers define a schedule when a watch is automatically executed:
It is okay for watches to have no trigger. But then, you have to trigger them externally via the API. This is for cases where you want to “push” events from external systems into Signals:
Yes, this is a good idea. I’ll start a new thread for the LDAP-related question: