Pause

Description

Use the Pause step to delay further scheme processing for a specified time period.

Typical use cases:

Wait for PNR synchronization (for example, when receiving an airline record locator for low-access carriers)
Wait for SSR confirmation
Wait for a customer response after sending an email notification

If the scheme is modified while the PNR is on pause, processing will resume using the updated version of the scheme after the pause period expires.

Recommendations and limitations

Use Pause only for short delays (recommended up to 24 hours).

Settings

Configure how long the PNR should remain on pause.

Resume processing after a fixed time interval.
Resume processing on a specific calendar date.

ℹ Note: The pause is ignored if the PNR reaches this step after the specified time.

Resume processing relative to an operational event.

For PNR processing schemes:

before the first upcoming flight segment
before the ticketing time limit expires
after completion of the last segment

For ticket processing schemes:

after original departure
after ticket has been issued
after travel has been completed

⚠ Important: If processing resumes after midnight in PNR pricing schemes, pricing may fail. Consider using the Event condition before Pause to avoid this.

Workflow behavior

After the pause expires, the system re-runs the Start element of the same scheme and checks the PNR against the Start conditions again.

If the PNR still matches the Start criteria, processing continues from the step following Pause.

Processing may resume earlier if:

another scheme triggers immediate processing of this scheme
a manual restart is performed (for example, via ingest or monitor)

Notes