This article explains how the Repeat element works and how to configure it.
When the Repeat step is reached, the system stops the current instance and schedules a new execution. At the defined time, the scheme starts again from the Start step, and the PNR or ticket passes all checks and actions configured in the workflow.
Use Repeat for long waiting periods when the workflow must restart from the beginning and reprocess all checks and actions.
Unlike the Pause step, Repeat always restarts the workflow from the beginning of the scheme.
Select one of the following options:
[ADD IMAGE]
Set a delay before the scheme runs again.
Select the reference point for the time calculation:
- later – calculate from the moment the PNR reaches this step
- before the first coming flight segment – count back from the departure time first upcoming segment
- before ticketing time limit expires – count back from the TTL
- after ticket has been issued – calculate from the ticket issuance time
- after original departure – calculate from the originally scheduled departure time
- after completion of the last segment – calculate from the completion time of the final segment
⚠ Available options depend on the scheme type and whether a PNR is required.
Restart processing at the specified date and time.
Use this option when processing must resume at a specific moment.
The execution time is calculated according to the system’s time zone.
Repeat processing according to a defined recurrence pattern.
Select the required frequency (minutes, hourly, daily, weekly, monthly, yearly, or custom), and define the start time and interval.
Each time the scheduled moment is reached, the system restarts the scheme from the Start step.
Execution time is calculated according to the system’s time zone.
Use this option for regular monitoring (for example, daily checks before departure or periodic fare validation).
The Timezone field displays the time zone used by the system to calculate and apply the repeat schedule. The value is predefined in the system settings and shown for reference only.
Delay processing for the configured time if the system cannot read the PNR or ticket.
The maximum postpone time can be defined in this field. The number of retry attempts is managed internally by the system.
When the calculated time is reached:
- The system restarts the scheme from the Start step.
- The PNR or ticket is re-evaluated, and processing continues according to the workflow.
⚠ If the configured repeat date or time has already passed, the scheme stops with a Fatal error.