Overview
The Operational Log keeps every RideOps dispatch and queue time for a Location. When an Operator forgets to log a dispatch, enters the wrong rider count, or counts guests on paper, you fix the record in the Backend: add the missing entry, edit it, or delete it.
This article covers adding, editing and deleting dispatch and queue time entries. To find entries and filter the log, see Log book on the web — the Operational Log dialog.
At a glance |
|
Who can do this | Super Users, or a Role with Operations › Manage Dispatch Entries (dispatches) or Operations › Manage Queue Entries (queue times) |
Where | Locations › select one Location › View Operational Log |
Works on | Backend (web) |
Availability | All organizations, for Locations with RideOps turned on |
💡 Why this matters: Throughput, utilization and queue reports are built from these entries. A missed or mistyped dispatch skews every RideOps dashboard widget for that day, so correcting it keeps your reports honest.
What you can change here
Entry | In this dialog |
Dispatch and Update Queue (from RideOps or added here) | Add, edit and delete |
External Dispatch and External Update Queue (from an integration such as Safari AI) | View only |
Openings, closings and uptime periods | View only. Correct them in the Uptime Summary with Create Period, Edit Period, Add downtime for this period and Delete Period |
Sign-ins, Notes, Assignments, Downtimes, Results | View only. Open takes you to the Note, Assignment, Downtime or Result |
Create Activity only appears on Locations with RideOps turned on. See Setting up RideOps.
Add a missing entry
1. Open the Operational Log
In the Backend, go to Locations, select the Location and click View Operational Log in the toolbar.
2. Click Create Activity
Click Create Activity (the + button). The Create Operational Activity dialog opens.
3. Fill in the entry
Choose the Activity Type, Riders Dispatch or Queue Time, then set the Date (date and time; it can’t be in the future) and the Operator it’s recorded against. Then fill in the fields for that type:
Field | What to enter | Starts at |
Riders | Guests on the dispatch (or on all of them, see below) | Empty, required |
Dispatches | How many dispatches to add, at least 1. Only when adding | 1 |
Cars in use | Cars or units running, at least 1 | The Location’s RideOps dispatch units |
Available seats | Seats per car, at least 1 | The Location’s RideOps seats per unit |
Unavailable seats | Seats out of use across all cars | 0 |
Queue in minutes | The wait time. Queue Time only | Empty, required; can’t exceed the Location’s maximum queue time |
Click Save (the check mark).
⚠️ Heads-up: When Dispatches is more than 1, Mobaro adds that many entries one millisecond apart and puts all the Riders on the first one. The others show as Dispatched 0 riders. RideOps does the same when an Operator enters dispatches and riders at closing. The day’s totals are still right.
Edit an entry
1. Find the entry
In Completed, pick the time range and tick Dispatch or Update Queue in Activities. Select the entry.
2. Change the values
Click Edit Activity (the pencil). In Edit Operational Activity, change the Operator, Riders, Cars in use, Available seats, Unavailable seats or Queue in minutes, then click Save. The Activity Type and Date are locked; to move an entry to another time, delete it and add a new one.
Delete an entry
Select a Dispatch or Update Queue entry, click Delete Activity (the bin) and confirm with Yes. You delete one entry at a time.
🛑 Critical: Deleting an entry can’t be undone. It is removed from the log and from every report and RideOps dashboard widget that counted it. Check the time and values before you click Yes.
Where your changes show up
RideOps dashboard widgets and statistics with the source set to RideOps. See RideOps dashboard widgets.
Webhooks: adding or editing sends an Updated event, and deleting sends a Deleted event, to webhooks for Dispatches or Queue times. See Using webhooks in Mobaro.
Not the Attractions.io guest app: it only receives queue times posted in RideOps. See Set up the Attractions.io integration for RideOps.
Best practices
Correct entries the same day, while the Operator still remembers what happened.
Record the real Operator, not yourself, so per-Operator reviews stay accurate.
For a day’s total counted on paper, add one entry with Riders as the total and Dispatches as the number of cycles.
Keep Operations › Manage Dispatch Entries and Manage Queue Entries for supervisors who review the data.
Frequently asked questions
Can rider counts be added to a previous day?
Yes. Click Create Activity, choose Riders Dispatch and set the Date to that day. Any past date and time works; future times don’t.
Someone entered too many riders on a dispatch. Can I change it?
Yes. Select the entry, click Edit Activity, correct Riders and click Save. You can’t change the number of dispatches on an existing entry; delete extra entries instead.
We enter dispatches and riders at closing. Why does the log show dispatches with 0 riders?
That’s expected. Mobaro puts all the riders on the first dispatch and adds the rest with 0 riders, so the totals for the day are correct.
As a Super User, can I adjust queue times from the desktop?
Yes. Add or edit an Update Queue entry in the Operational Log. It updates Mobaro’s records and reports, but it isn’t sent to the Attractions.io guest app.
Can I delete everything in the Operational Log at once?
No. Dispatch and queue entries are deleted one at a time with Delete Activity, and uptime periods one at a time in the Uptime Summary.
Why can’t I edit a Safari AI dispatch or queue time?
Entries from integrations (External Dispatch, External Update Queue) are view only. Only entries from RideOps or added in this dialog can be edited or deleted.