Overview
This section explains how Triggers are executed, provides modeling recommendations, and describes how to identify and troubleshoot execution issues.
Execution
All emails considered for Triggers and Actions must be sent to the email inbox provided by Bizagi. Once the email is received, a recurring job monitors the inbox for new unread messages.
The recurrent job analyzes the content of the email and assesses if it matches the conditions of configured Triggers. If a match is found, Bizagi places the corresponding action in a queue for execution. For example, the action may start a case in the Claims and Complaints process.
Finally, the case is started when the queue is executed.
|
|---|
Once an email is marked as read, it is not considered by other Triggers. |
Activate two or more processes from the same email
If an email matches the conditions of two or more Triggers, only one Trigger is executed. Bizagi executes the Trigger that was most recently created or modified.
If you need to start cases in multiple processes from the same email, we recommend modeling a dispatcher process. Consider the following example.
You need to activate two processes:
•Credit card request
•Vehicle loan request
Use a single Trigger with conditions that identify emails for either process.
If an email matches both conditions, the dispatcher process can create the corresponding Credit Card Request and Vehicle Loan Request cases.
For further information about how to create cases from a process, refer to Create a new case.
To verify Trigger execution or investigate potential issues, Bizagi provides Trigger's tracing. You can enable it from the Management Console of the environment you want to review.
Select the Track section, click Tracing, and expand the Triggers and Actions node. Right-click Processing and Monitoring Trace and select the level you want to log (Information, Warnings, or Errors).
|
|---|
Only activate tracing options when needed. Otherwise, leave this option off. |
When facing problems, we suggest the following steps:
1. Check the email address you are sending messages to. A misspelling in the mailbox name results in a "mail not found" error in your email client. Please check the naming rules for your specific scenario. When in doubt, contact Bizagi support to get the current mailbox name.
2. Check the Trigger conditions used when setting up the Trigger. Sometimes a condition is too restrictive and prevents the Trigger from being activated. Try loosening or removing the condition.
3. Check OAuth permissions. In the OAuth applications administration feature in Bizagi Work Portal, review the OAuth endpoint, used by Triggers & Actions. Check if the set up has access to the process you selected in the trigger action. Even if the OAuth application was setup automatically, there may be the case the user was changed to one with fewer permissions.
If OAuth has not been configured correctly, review the Management Console traces for additional details.
4. Check OAuth configuration. As explained above, you can review specific details of the OAuth endpoint used by Triggers & Actions in the OAuth applications administration feature in Bizagi Work Portal. Verify that values such as the client ID, client secret, and URLs match those configured in the Triggers & Actions feature in Bizagi Studio.
5. Review traces. If nothing of the above works, review Trace files as explained above. You will find detailed information about details like how emails are processed, which trigger conditions are met, what happens when calling the OData endpoint of Bizagi Automation Services, and more.
Last Updated 10/2/2026 9:37:49 AM