These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Theme Park Management
- Features
- Operations control
Operations control
Operation receipts, exceptions and reconciliation.
OverviewOperation exceptions×
Theme Park Management · Operations control
New
Operation exceptions
Operation receipts
| Id | Operation key | Action | Parent | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| IDD-536 | OK-508 | ACT-144 | EVN-11969 | Pending | 17 Oct | |
| IDD-763 | OK-674 | ACT-944 | EVN-26180 | Failed | 16 Oct | |
| IDD-170 | OK-445 | ACT-600 | EVN-87729 | Needs review | 24 Oct | |
| IDD-288 | OK-313 | ACT-238 | EVN-61653 | Pending | 21 Oct | |
| IDD-288 | OK-933 | ACT-976 | EVN-40433 | Failed | 11 Oct |
6 of 6 records
IDD-536Operation receipts · OR-78665
PendingOperation keyOK-508
ActionACT-144
ParentEVN-11969
Occurred at17 Oct
Failure reasonCut to length
What you can do
Know every approval, scan and close took effect
Every guarded action, whether approving an event, reserving and admitting, releasing a ride session, closing or cancelling, writes an operation receipt. The receipt holds a stable key, the action, the revision expected, the time and a result: pending, completed, failed or needs review. It lists the effects the action should have produced and, when something went wrong, the reason.
On a busy day connections drop and devices retry. Receipts make that safe: a repeated action returns the first result. Reconciliation reads what was actually saved before it marks a receipt completed. It never repeats an external payment action. When it cannot confirm an outside result, the receipt stays marked for review rather than being assumed complete.
How the work is organized
The park operations manager watches the exception queue.
- One key, one effect. Each operation key takes effect once.
- Read first. Completion is confirmed from saved records.
- Unclear stays open. Receipts that cannot be confirmed are marked for review.
What to agree during setup
Agree who checks the exception queue during the day and at close, and how often reconciliation runs. Prepare examples of a completed approval, a timed-out admission scan that did complete, one that did not, and a refund with no provider confirmation yet.
Check the handoff on an actual case
During the lunch rush a gate loses connection and several scans are retried. Their receipts show one admission per ticket. At close, reconciliation finds one cancellation whose refund the provider has not yet confirmed, so its receipt stays in the queue for the payments clerk instead of being counted as done.
The next morning the manager checks the queue before opening. Only that one refund is still waiting, and the payments clerk follows it up with the provider.
Over a season the queue also shows where problems repeat, such as one gate that drops its connection every busy afternoon. The operations manager can fix the cause instead of clearing the same exceptions day after day.
What your team sees
- Operation exceptions — Pending, failed and needs-review receipts with their reason.
Follow the work through
- Event close and reconciliation: Closing the day cleanly.
What it keeps track of
Data model- Operation receipts
- Durable receipts for guarded operations with stable operation keys.
- Events
- Park operating events with capacity, lifecycle and revision control.
Who uses it
Permissions- The manager follows exceptions and closes the day.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.