The Pause element temporarily stops scheme execution.
The Pause element temporarily suspends scheme execution for a limited period of time (up to 24 hours).
It is used in scenarios where further processing must be delayed to allow external systems, carriers, or passengers to complete required actions.
Typical use cases include:
- Waiting for airline record locators to be returned for newly booked segments
- Awaiting confirmation of SSR services
- Waiting for a passenger’s response to an email sent by the scheme
When a PNR enters the Pause element, its processing is suspended. After the pause period expires, the system fully re-executes the Start element of the same scheme, re-validating the PNR against the Start conditions.
If the PNR still matches the Start criteria, processing resumes from the element immediately following Pause.
This ensures that the scheme continues only if the PNR remains relevant at the moment of resumption.
Pay special attention to the following scenarios:
- Editing the scheme while PNRs are paused Removing the Pause element or reconnecting its outgoing path to a different branch may cause PNRs currently in Pause to become stuck and not resume processing.
- Processing triggered by another scheme If the same PNR is reprocessed by another scheme (including Ingest), it will be removed from the Pause state and processing will resume immediately.
- Delay processing without terminating the scheme
- Wait for carrier-side or passenger-side confirmation
- Ensure controlled, time-bound continuation of PNR processing