Report bursting schedules are executed like a normal report scheduling. Pausing the report-bursting process essentially puts it on hold. The process stops at the point where it was paused. If report bursting is resumed, it fires the missed schedules once and continues with the next upcoming instances based on the given frequency. For example, when a report bursting is paused on August 1 and resumed on August 15, it kick-starts the report bursting on August 15 and continues with the next upcoming instances based on the given frequency.
You can retry failed burst schedules, pause, resume, or delete burst schedules.
...