Overview
Use Add downtime for this period when an interruption needs to be added after the operating period has ended. Start from the relevant completed uptime period so the historical interruption is connected to the right Location and operating record.
At a glance |
|
Who can do this | Super Users or Operations › Manage Downtime, with access to the Location. |
Where | Locations › Uptime Summary |
Works on | Backend (web) |
Availability | All organizations |
💡 Why this matters: Recording the actual interruption against its operating period helps keep later operational reporting explainable.
Before you start
The illustrations use an operating period from 09:00 to 17:00 and an interruption from 11:15 to 11:45. Confirm your own real times from the operating records. This is historical record maintenance, not the live fault-reporting workflow or authorization to reopen a ride. If the period already has a linked Downtime, inspect that record rather than creating another.
Walkthrough
1. Select the completed uptime period
Open the Location’s Uptime Summary and select the relevant ended period. Check its opening and closing times and the displayed time zone. Add downtime for this period is available only for a closed period without a linked Downtime and with the required permission.
2. Enter the interruption times
Select Add downtime for this period. Set Starts at and Ends at from the agreed event record. The start picker is bounded by the selected uptime period; do not accept a prefilled value without checking it.
3. Describe and categorize the event
Add a useful Description, select the appropriate Downtime Categories and attach available supporting evidence. Distinguish the reason for the interruption from the action taken afterwards.
4. Keep the historical correction separate from new work
Leave Create Assignment off when the interruption was already dealt with. Creating new work here can affect the Location’s current readiness. Select Add, then inspect the saved historical record. If a repair is still outstanding, arrange and verify its Assignment separately through your normal maintenance process.
Check the outcome
Mobaro ends the selected uptime period at the interruption’s start. If the interruption ends before the period’s original close, the remaining time becomes a new uptime period. The closed Downtime’s duration is its end minus start, rounded up to whole minutes, without trimming to opening hours. In the illustrated example, check for uptime periods 09:00–11:15 and 11:45–17:00, plus 30 minutes of Downtime. Check the resulting records and reporting view after saving. Historical entry is not a substitute for completing any outstanding maintenance or operational handover. For changes to existing periods, follow the Uptime Summary guide and the Downtime lifecycle.
Best practices
Use recorded event times rather than memory where available.
Check for an existing linked Downtime first.
Keep historical record corrections attributable and described.
Frequently asked questions
Why is Add downtime for this period unavailable?
Select one ended uptime period that has no linked Downtime. You also need Super User status or Operations › Manage Downtime.
Can I correct times that were logged earlier?
Authorized administrators can maintain the underlying operational records. First decide whether the error is in the uptime period or Downtime record; see the correction guide.
Must every historical entry create an Assignment?
No. Leave Create Assignment off for this historical correction. It is separate from deciding whether current maintenance work is still needed.