Failed Import Runbook

Use This During Live Operations

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Failed Import Runbook narrows that work to recovery steps when an EMS LAN import fails, is rejected, or has suspicious counts. Because this is a runbooks page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Runbook Stabilizes

This page is for a pressured moment. Use the sequence to slow the work down, assign ownership, protect records, and leave a clear next step. The intended readers are Import operators and Support leads. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/offline-snapshot?id=:eventId.
• Records or contracts involved: Import attempts and Snapshot files.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Move From Situation To Handoff

1. Name the live situation: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Failed Import Runbook.
2. Assign the operator and reviewer: Use /rego/events/manage/offline-snapshot?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Perform the smallest safe action: Keep Import attempts and Snapshot files in view so the work stays tied to the records or contracts it can affect.
4. Write the handoff before the next person takes over: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

The Runbook Is Complete When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook when import does not succeed cleanly.

1. Step 1 - Stabilize the situation. Confirm the dashboard event ID, filename, file format, and visible error. This gives support leads the minimum evidence.
2. Step 2 - Choose the current source of truth. Check whether the file is stale, wrong-event, damaged, unsigned, unsupported, or not final. This narrows the failure cause.
3. Step 3 - Execute the scenario path. Do not retry repeatedly. Preserve the file and error message, then ask the event lead or support lead to decide the next attempt. This avoids making the trail noisy.
4. Step 4 - Pause at every risk marker. Confirm whether onsite operations are still continuing and whether another file may arrive later. This prevents importing a partial file.
5. Step 5 - Capture proof before the team moves on. Check LAN Sync History to see whether any import entry was created. This tells you whether anything applied.
6. Step 6 - Debrief and hand off unresolved work. Record the failure and recovery decision before another import attempt. This preserves accountability.

Common causes

• The file belongs to another event.
• The file is not the final LAN output.
• The file is damaged or incomplete.
• The hosted API cannot verify expected snapshot structure.
• The operator is using the wrong dashboard route or role.