Skip to main content

Celonis Product Documentation

Triggers FAQs

To check for Record Items that match your criteria, your Trigger evaluates the logic, compares it to the previous check, and triggers the Action Flow for newly detected items. This happens on the following occasions:

  • Whenever a Data Model is reloaded which is when new data gets injected into the Data Model.

  • Whenever the definition of the Trigger is updated that is when the Knowledge Model gets published).

Changes in the Trigger logic are treated the same as changes of the data. This way, we ensure that every new item gets added to the results in an execution, regardless whether it was added due to a change of a filter or new data.

If your use case requires a different trigger behavior, let us know in the feedback form. For the moment, if you want to avoid executions for items detected as new just because of a logic change, you can deactivate the Action Flow while performing the changes, and remove the items from the Action Flow Webhook Queue before activating the Action Flow again.

When starting to watch a Trigger, the Trigger will only be executed for new items. We will offer support to also trigger for existing items in the future. For the moment, the only workaround if such a capability is needed is to “reset the Trigger” by adding a filter that filters out all items, publish the trigger definition, and then remove this filter again.

The connection used in the Action Flow governs data visibility and permissions. When watching a trigger, a subscription on the Trigger is created which will detect new items the connection has access to.

In your Knowledge Mode, select triggers for the overview of all Triggers available in the Knowledge Model. Click the Trigger that you’re interested in. For every Trigger that is in use, you can click on the “In Use” Icon in the Trigger header to open a screen with operational details about the specific Trigger.

If the Action Flow is not set to execute immediately (being inactive or switched to scheduled execution), the execution requests for new items are stored on the webhook queue. Keep in mind that there is a limit on that queue of 10k items. If that limit is reached, the webhook won't store new requests anymore. Currently, those requests are lost. Consider this when designing such a solution.