Capture the interruption timeline
Record when the broadcast stopped, when it resumed and whether its target identifier changed. Keep the order ID alongside these times so support can relate the interruption to the purchased service window.
Check the purchased time rules
Read how the service treats offline periods, early endings or a restarted session. Some questions require support clarification; the buyer should not invent a pause-and-resume entitlement where the description provides none.
Avoid overlapping recovery orders
Confirm the original request's state before purchasing another session. A restart does not establish that the old order ended financially, and a new purchase may introduce overlapping charges or activity if the first request continues.
Decision checklist
| Decision | What to check |
|---|---|
| Timeline | Stop and restart times with timezone |
| Session | Same or changed target identifier |
| Resolution | Documented treatment of interrupted time |
Worked example
In a hypothetical one-hour broadcast, the connection fails after twenty minutes and returns ten minutes later. The buyer sends that timeline with the order ID. The missing ten minutes are not automatically added to the package without confirmation of the applicable terms.
Example figures explain the decision; they are not current prices or promised results.