Creating an event trigger

Important: Event triggers that are created at design-time using event trigger activities can be further configured at process-creation time, in Orchestrator, as these types of triggers are identified as package requirements. Read Managing package requirements > Adding event triggers to find out more.

To configure event triggers in Integration Service, read the Configuring event triggers section.

To configure event triggers at process-creation time, in Orchestrator:

1. After Orchestrator displays the event trigger as a package requirement, click the corresponding Update Trigger button. The Edit Event Trigger page opens. This step is optional. Default selections apply if ignored.
2. Provide a unique Name for your event trigger. Duplicates are identified in the package requirements tab, with the Duplicate name status.
   Note: The Process Name is prefilled and you cannot change it in this step.
3. Set the Job Priority.
4. Select the Runtime type. If you want to use an unattended runtime, we recommend not setting the connection as Configurable by users.
5. Turn on the Schedule ending of job execution toggle to select a job termination strategy.
   Note: The amount of time specified here elapses according to the specifications, even if the job is queued. For example, if you schedule a job to run at 1 p.m. and set it to stop after 20 minutes, the job stops at 1:20 p.m. even if it had stayed in a queue until 1:15 p.m., and then started.

   Additionally, if you schedule to stop a Pending or Running job after 2 hours and also configure to kill the same job after 3 hours, the job will be killed after 5 hours. This happens because, first, the signal is sent to Orchestrator that the job was indeed stopped after 2 hours. Once the signal has been received, the kill job action is triggered to occur in 3 hours, thus resulting a total of 5 hours.

   • Select Stop from the drop-down - attempts to gracefully end the execution after the defined time interval has passed since the job is stuck in a Pending or Running state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes);
     Example: Orchestrator will attempt to stop jobs that have been stuck for at least 10 minutes in Pending or Running.

     

   • Select Kill from the drop-down - attempts to forcefully end the execution after the defined time interval has passed since the job is stuck in a Pending or Running state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes);

     Example: Orchestrator will attempt to kill jobs that have been stuck for at least 10 minutes in Pending or Running.

   • Select Stop from the drop-down and enable the If the job does not stop, kill it option - attempts to gracefully end the execution after the defined time interval has passed since the job is stuck in a Pending or Running state and then attempts to forcefully end it after the defined time interval has passed since the job is stuck in a Stopping state (set the time to a minimum of 1 minute, maximum of 10 days, 23 hours and 59 minutes).

     Example: Orchestrator will attempt to stop jobs that have been stuck in Pending or Running for at least 10 minutes. If the termination does not happen, Orchestrator will attempt killing those jobs that have been Stopping for at least 20 minutes.

6. Turn on the Generate an alert if the job is stuck (in pending or resumed status) toggle, and set the acceptable duration for the job to remain in the pending or resumed status. The minimum configurable duration is one minute. The maximum configurable duration is eleven days. If the job exceeds the configured duration, an "Error" severity alert pop-up informs you about it with the following text:"N jobs for #process {process_number} have been pending or resumed for more than X hours and Y minutes.", where:
   • N - is the number of jobs that triggered the alert;
   • {process_number} - the process identifier;
   • X - the configured number of hours the job exceeded while having the pending or resumed status; Days are converted to hours.
   • Y - the configured number of minutes the job exceeded while having the pending or resumed status.
7. Turn on the Generate an alert if the job started and has not completed toggle, and set the acceptable duration for the job to complete. The configurable duration is minimum one minute and maximum eleven days. If the job exceeds the configured duration, an "Error" severity alert pop-up informs you about it with the following text: "Job for #process {process_number} has been pending been running for more than X hours and Y minutes.", where:
   • {process_number} - the process identifier;
   • X - the configured number of hours the job exceeded while trying to complete; Days are converted to hours.
   • Y - the configured number of minutes the job exceeded while trying to complete.
8. Click Update. This updates the Orchestrator configuration of the event trigger.
9. Click Next to continue configuring the process, and then click Create.

Note:

Execution-based trigger disabling

This applies only to event triggers published from Studio Web to personal workspaces.

By default, triggers are disabled after 5 consecutive failed executions. You can choose to change this setting with the help of the following tenant-level execution settings:

• Triggers - Connected triggers - Disable when job execution fail count

• Triggers - Connected triggers - Grace period when job execution keeps failing count (days)