4. Ops Alert Catalog

Last updated: September 8, 2026

How alerts work

  • They update on their own, fast. The board refreshes every few seconds, so alerts show up and clear almost as things happen.

  • One alert per problem. You won't get a pile of duplicates for the same issue. While an alert is open, the system won't raise another one for it.

  • They clear themselves. An alert opens, you can acknowledge it, and it resolves on its own once the problem goes away. Don't manually clear one while the issue is still happening – it'll just come back. (A few don't auto-clear; those are noted on the alert.)

  • Moving an order forward clears some for you. When you manually advance an order's status, that automatically clears the related timing alerts on it (dispatch SLA, stuck status, load SLA, customer handoff stuck, nav not started, and nav ends away from delivery point).

  • Two alerts let you act from the card. Dispatch SLA and Vehicle stationary have a Reassign button right on the alert. Every other alert opens the order when you click it, so you work it there.

Severity: critical (act now) · warning (investigate) · info (awareness only).


Before the Supervisor leaves – assignment and quoting

Assignment held · assignment_held · critical · ~1 min after it's held

  • Fires: a scheduled order has no vehicle and the system is holding it back instead of assigning it. It flags about a minute after the hold starts. (Older orders that were never formally held flag once they're more than 10 minutes past their ready-by.) The alert title tells you why it's held.

  • Clears: the order gets a vehicle, moves out of scheduled, or is cancelled.

  • Means: nobody's coming for this order and the system can't place it on its own. Check the reason on the alert, then reassign it, batch it onto a run, or cancel it.

Dispatch SLA breached · dispatch_sla · critical · 3 min assigned, not moving · Reassign on the card

  • Fires: an order's been assigned to a Supervisor for more than 3 minutes and they still haven't started toward the store. (If the vehicle is already at the store when assigned, this never fires.)

  • Clears: the order leaves "assigned" – the Supervisor departs, or it's reassigned or cancelled.

  • Means: the Supervisor has the order but isn't moving. Reassign from the card, or contact the Supervisor.

Quote expiring · quote_expiring · info · 1 min before it expires

  • Fires: a quote the retailer hasn't turned into an order is about a minute from expiring.

  • Clears: the quote gets used, cancelled, or expires.

  • Means: the retailer's about to lose the quote. Awareness only – you can't extend it.


At the store – store leg and loading

Stuck in status · stuck_status · warning · varies by status

  • Fires: an order sits in one status too long. The limits:

Status

Limit

Heading to the store

15 min

At the store

5 min – from when the food's due, so waiting on the kitchen doesn't count

Waiting to load

10 min

Heading to the customer

15 min

At the customer

5 min

  • Clears: the order moves to the next status.

  • Means: one leg is taking longer than it should. Check where the vehicle actually is before you advance it.

Next stop not staged · stuck_status · warning · 10 min after the last stop

  • Fires: a run out delivering finished a stop, but its next stop hasn't been set up, and it's been more than 10 minutes.

  • Clears: the next stop gets set up, or the run finishes delivering.

  • Means: on a batched run, the handoff to the next order didn't happen. Manually advance the next order to fix it.

Load SLA breached · load_sla_breach · info · 5 min waiting to load

  • Fires: the trunk's open for loading but the order's been waiting to load more than 5 minutes.

  • Clears: the order loads, or moves further along.

  • Means: the Supervisor's at the store with the trunk open and the food isn't in yet. Nudge the Supervisor.


To the customer – navigation and handoff

Nav never started · nav_not_started · warning · 10 min after the stop was set up · doesn't auto-clear

  • Fires: a stop's been set up but the order's still loaded 10 minutes later – the navigation that should have sent the car to the customer never went through. The alert shows how many nav attempts failed.

  • Clears: the order leaves "loaded" state (nav sends, you advance it, or it's cancelled/failed).

  • Means: the car was never sent to the customer. This also pops up right after you manually complete the previous stop, since that sets up the next stop without sending navigation. Have the Supervisor start nav, or advance the order yourself.

Nav not engaged · nav_not_engaged · warning · after a re-send with no route · doesn't auto-clear

  • Fires: the system re-sent the navigation to the car and still sees no sign it's driving there (no route, no ETA). Holds while the order's heading to the customer with no route yet.

  • Clears: the car shows a route (Supervisor started nav or typed the address), or the leg ends.

  • Means: the car got the destination but nobody started driving to it. Reach the Supervisor to start navigation by hand.

Nav ends away from delivery point · nav_terminus_variance · warning · more than 200 m off · doesn't auto-clear

  • Fires: the car's heading to the customer but the end of its route is more than 200 meters from where we have the customer's poin (normal is under 50m). The alert displays both locations; if the address was already shaky, it suggests using the car's destination.

  • Clears: you change the address, the leg ends, or the gap drops back under the 200m limit.

  • Means: the car's driving to a different spot than where we think the customer is – usually a bad pin. Use change-address; the car's endpoint is your best correction.

Customer handoff stuck · customer_handoff_stuck · warning · 10 min at the customer

  • Fires: the order's been at the customer's address more than 10 minutes without completing.

  • Clears: the order completes, fails, or is cancelled.

  • Means: the vehicle's there and the customer hasn't picked up the order. Contact the customer; if they can't retrieve it, consider the undeliverable path.


Vehicle health – telemetry and safety, keyed per vehicle

Telemetry stale · telemetry_loss · warning · 5 min with no location

  • Fires: a vehicle that should be moving (heading to the store or customer) hasn't reported its location in more than 5 minutes. Parked statuses (at the store, loading, loaded, at the customer) don't count, since Teslas go quiet when parked.

  • Clears: a fresh location comes in, or the vehicle has no active leg.

  • Means: we can't see a car that should be moving – dead signal, a sleeping vehicle, or the telemetry feed.

Vehicle stationary while en route · vehicle_stationary · warning → critical · 5 min → 15 min · Reassign on the card

  • Fires: a vehicle that should be moving hasn't gone more than 25 meters in over 5 minutes. It escalates to critical at 15 minutes.

  • Clears: the vehicle moves, or the order's no longer in transit.

  • Means: the car's reporting but not going anywhere – traffic, a stop, or a Supervisor who pulled over. Different from telemetry loss (there, we can't see it at all). Contact the Supervisor or Reassign from the card.

Autopilot disengaged · disengagement · critical · when it happens · doesn't auto-clear

  • Fires: a Tesla autopilot disengagement on a pilot vehicle – either reported by the car or logged with the "Log disengagement" button in the order. One alert each time it happens.

  • Clears: you acknowledge it.

  • Means: the car handed driving control back to the safety Supervisor. It's a safety record, not a delivery problem on its own.


Whole order – age, failure and evidence

Whole-order breach · whole_order_breach · warning → critical · 60 min → 90 min old

  • Fires: an order that hasn't finished, failed, or been cancelled passes 60 minutes old (warning) or 90 minutes (critical). Both can show at once.

  • Clears: the order finishes, fails, or is cancelled. Advancing it partway doesn't clear it.

  • Means: whatever step it's on, this order is late start to finish.

Undeliverable after load · undeliverable · warning · when an order fails after loading

  • Fires: an order marked failed that had already been loaded – so the food left the store in a vehicle. Orders that failed before loading don't count.

  • Clears: the order leaves "failed" (retried, returned, or cancelled).

  • Means: there's an order in a vehicle with nowhere to go. Decide: back to the store, or try again.

Proof photo still pending · photo_pending · warning · 10 min after completion · doesn't auto-clear

  • Fires: a pickup or delivery was completed with the photo still uploading, and 10 minutes later it hasn't attached.

  • Clears: the photo attaches.

  • Means: the proof photo's still stuck on the Supervisor's phone. Have them open the app while online so it uploads.


For your information – event-driven, no auto-clear

Order re-pooled or cancelled · ops_action_fyi · info · when it happens

  • Fires: an order was cancelled (by the retailer, the Supervisor flow, or from the console), or a Supervisor rejected it and it went back to the queue.

  • Clears: you acknowledge it.

  • Means: tells you why an order moved, without digging through the log.

Delivery pin auto-corrected · geocode_pin_swap · info · when it happens

  • Fires: the system moved a customer's delivery pin on its own because its address check found a better spot. The alert shows how far it moved and both locations.

  • Clears: you acknowledge it.

  • Means: double-check the new pin. If it looks wrong, fix it with change-address.