When desired, routing triggers can be set up to execute form actions at specific dates, or after certain amounts of time have elapsed, turning them into "timed routing triggers." For more information on creating these triggers, visit ATLAS Formbuilder - Timed Routing Triggers.

Unlike triggers that evaluate their conditions every time the form response is saved, timed routing triggers add form responses to a queue system, and evaluate each response in the queue when the trigger's appropriate date has arrived, or when the appropriate amount of time has elapsed.

The presence of a form response in a timed routing trigger's queue is not a guarantee that the response will be executed. It is only a guarantee that at the trigger's specified evaluation time, the response will be evaluated according to the trigger's conditions. If the conditions are met, then the trigger will execute for that response.

The various ways that a form response can be added to a routing trigger queue are as follows:

• The timed routing trigger is duplicated, archived, or modified and saved.
• The period that a form response exists in is saved (a date-based trigger may refer to a period's start/end dates).
• The form response is saved...
  • via the survey view 
  • via the admin interface and modified such that a routing trigger is executed.
  • via the FormBuilder webservice.
  • via an aggregate form view.
• An event registration form response's waitlist/registration status is updated...
  • via automatic waitlist management.
  • via the admin interface.
• Another of the form's routing triggers executes (includes all types of routing actions, across both timed and non-timed routing triggers).

To access a timed trigger's queue, click on the gear icon next to the trigger's listing on the form's Routing Triggers page, and select View Queue from the dropdown menu. A preview of the number of form responses currently in the queue will be displayed next to this menu option.

There is no limit to the amount of times that a form response can be added to a trigger's queue. If there is concern about a time-based trigger executing multiple times due to its condition continuing to be met, it is paramount that a cap is placed on the number of times the trigger can execute using the "Number of triggers per..." options in its Properties settings.

For information on editing a trigger's properties, visit ATLAS FormBuilder - Adding and Editing Routing Triggers.

For more tutorials and articles on ATLAS FormBuilder, visit FormBuilder - Homepage.