# Report Resumption

In general, any incomplete report will be resumed in a subsequent session.

There are some idiosyncrasies and limitations as listed below:

- At any given time, it is possible that multiple distinct report types could be incomplete to the same destination. In this case, resumption will happen according to current session priorities and rotation rules.
- Program mode will only reset those session schedules that were modified. The resumption status is cleared only if a schedule change made the session no longer pending.
- The only procedures that globally impact the session resumption states are:
  1. Disarm/Arm.
  2. Exporting the Alarmware data base to RTU.

- Cycling power: any session in progress when power goes off will be resumed only if that attempt was already resumption. Any other sessions should have their resumption state survive the power cycle. However, all the history of what was reported is lost. The report will “resume” from the beginning.
- The “until reported” rule resumes any session that fails to report all required items.
- The “only once” delivery rule will only resume log file reports after contact established.
- The “continually until acknowledged” rule will resume acknowledgment, status, and log file sessions. Alarm reports always restart from the beginning.
- Callback sessions are never resumed.
- Cover page for report will indicate if current session is a “resumption of prior report…”
- Resumption may occur even if prior session not officially “contacted”.
- Fax sessions are limited (and hence might need resumption) only if some other session is waiting. Alpha pagers are always limited, even if no other session is waiting.