Automating your business is important, and when that automation doesn’t work as expected figuring out why is critical. When your automation is uses Triggers, you can troubleshoot issues by viewing the Trigger History.
Finding Trigger History Records
A link on the Trigger page navigates users to the Trigger History page.
The trigger history search allows users to narrow down to a specific trigger or action to expedite troubleshooting.
The default search filters are for the current day; however, you can increase the date timeframe to up to 30 days. Specifying additional criteria will help narrow down your search. The Name field is the Name of your Trigger.
We recommend you apply as many filters are possible.
The Results field contains several values that will help you determine what happened when the system ran your automation.
Completed Successfully | The trigger filters match and the system ran the configured action. |
Errored | The trigger filter matched but the action could not run successfully. |
Filter Did Not Match | A trigger is configured for the event that occurred but the filters did not match so the system did not run an action. |
Trigger Disabled | A trigger is configured for the event that occurred but the trigger is disabled. |
Understanding Trigger History Results
The search results will display by descending dates. To assist with troubleshooting the last three columns will provide helpful information – starting with the results.
Completed Successfully
You configured your trigger and did not receive the expected results so why does the system display Completed Successfully? When in this situation, it might be that the trigger configuration and action are valid but the action configuration may need adjusted.
For example, When an adjustment is created by CCOA and the amount is less than $25.00 the system will send a templated email to ccoat@idibilling.com. The trigger history would produce a result of Completed Successfully. The email however will not contain the smart data replacements as expected because the configuration of the data field in the action not valid.
Errored
When the system cannot execute your trigger the error result, plus access to the error message will be available to help correct the issue. The error message will provide information as to which business rules caused the error. The logging message ID is made available so that you can further research using the Web API documentation.
Filter Did Not Match
A trigger is configured for the event that occurred but the filters did not match so the system did not run an action. You will want to look at the filters within your trigger and make sure the message details from your event contains the values that match your filter. When you hover over a row within the results, the message detail icon will display 
. Click the icon to see details.
For example, using the trigger filters from above, if a $100.00 adjustment was created by CCOA and the trigger history result was that the filter did not match, the message details will help explain why.
In the message details above, I can conclude that I selected adjustment type was for a credit adjustment; therefore, the adjustment amount is a negative causing the filters to not match.
Trigger Disabled
A trigger is configured for the event that occurred but the trigger is disabled. This is a simple fix, just enable the trigger.