This action executes an action repetitively every specified interval (specified in milliseconds).

The action to be executed should appear inside Timer, and it should be repetitive. Its name is not important (the template of Timer includes a repetitive action Activity, but you can freely rename it or replace it with another action model).

The repetitive action can get any number of triggers that is needed. For each of these triggers, add a corresponding trigger to Timer itself, and make sure to create a flow from each trigger of Timer to the corresponding trigger of the repetitive action.

Triggers - Client Side

<Interval> (non-repetitive numeric trigger [required]): The interval (in milliseconds) between executions of the repetitive action.

The action is first invoked immediately, and then every <Interval> milliseconds (the interval is counted between the end of one invocation and the beginning of the next invocation, so it is safe to specify a interval shorter than the expected duration of the action).

To schedule a single delayed execution of a client side action, use Background Action.

Triggers - Server Side

<Delay> (non-repetitive numeric trigger [not required]): A interval (in milliseconds) before the first executions of the repetitive action. If both <Delay> and <First Time> are missing, the first invocation of the action is immediate.

<First Time> (non-repetitive date-and-time trigger [not required]): The date and time of the first executions of the repetitive action (an alternative to <Delay>, both triggers may not be used together). If both <Delay> and <First Time> are missing, the first invocation of the action is immediate.

<Interval> (non-repetitive numeric trigger [required, except as specified below]): The interval (in milliseconds) between executions of the repetitive action.

<Fixed Frequency> (non-repetitive Boolean trigger [not required]): If "Yes", an indication that the interval should be counted between successive invocation times of the action. If missing (or "No"), the interval is counted between the end of one invocation and the beginning of the next invocation, so it is safe to specify a interval shorter than the expected duration of the action).

To schedule a single delayed execution of the action (server side), remove the <Interval> trigger, add either the <Delay> trigger or the <First Time> trigger, and change the action to be non-repetitive.

Exit

<Timer Id> (non-repetitive numeric exit [not required]): A unique identifier of the timer instance (useful if you want to later cancel the timer through Cancel Timer).

Usage Example - Client Side