System Workflows
The engine-executed processes — states, timers, retries and jobs — that run the platform between and during human actions.
The user flows describe what people do. This section describes what the system does: every process with a state, a timer, a retry or a queue — the kind of process a workflow engine owns. The SRS cites a System workflows source document for these; these pages are that document, fully traced to the requirements.
Every page follows the same shape: the trigger, the actors, a diagram, the timers, and the stories the workflow serves.
The engine contract
All workflows in this section share the same execution rules, drawn from the SRS:
| Property | Rule | Trace |
|---|---|---|
| States | Every workflow is one of the ten state machines (SRS section 7) or a named pipeline below | SRS section 7 |
| Timers | Time-based transitions are guards on the state machine, with verbatim windows on each page | per machine |
| Retries | Payment callbacks at most once per gateway event identifier; notifications 3 times with exponential backoff; refunds 3 times; webhooks 5 times over 24 hours | FR-PAY-02, FR-NTF-05, FR-PAY-03, FR-ORG-06 |
| Idempotency | Idempotency keys are valid for 24 hours; duplicate replays are ignored by client event ID | SRS section 6.4, FR-CHK-05 |
| Jobs | Named scheduled jobs run the timers: daily, hourly, weekly and monthly cadences — see the job catalog | FR-ONB-04, FR-NTF-07, FR-ACC-03, FR-SUB-10 |
| Failure posture | The plan service fails closed; analytics and exports degrade without blocking bookings | FR-SUB-11, NFR-OBS-04 |
The workflows
Applications
Review, changes, appeals and re-application with working-day SLAs.
Booking & Payment
Seat holds, attempt caps, Fawry vouchers, gateway polls and escalation.
Refunds
Policy windows, coupon reversal, gateway retries and the post-cut-off path.
Trip Lifecycle
Publishing, start-time transitions, remedies and archival.
Trip Day
Check-in, offline queues, live tracking and moderator access windows.
Money
Ledger, weekly payouts, invoices, reconciliation and settlement closure.
Subscriptions
Trials, dunning on days 1-3-5-7, grace, downgrades and counter resets.
Notifications
Quiet hours, retries, deduplication and the reminder job.
Media
Upload windows, resumable batches, processing variants and archival.
Job Catalog
Every timer, queue and scheduled job on one page.
Reading the timers
Working-day SLAs (review in 2 working days, refunds sent within 2 working days) use the responsible party's market calendar. Clock timers (seat holds, quiet hours, payout runs) are absolute. Where the spec itself has not decided a value, the page says so with the open decision ID — those values follow the BRD open-decision process.
Stories in this section
Each workflow page carries user stories in the standard form — As a (role), I want (capability), so that (value) — each traced to the requirements it serves, so product, engineering and operations share one vocabulary.