When a report bursting is scheduled, it acts as normal scheduling. Pausing the report-bursting process essentially puts it on hold. The process stops at the point it was paused, which means that any reports that were in the queue to be generated, distributed, or processed would be halted. If it is resumed, it fires once for the missed schedules after the resume and continues with the next upcoming instances based on the given frequency.
Let us take a scenario where a user pauses the report bursting on August 1 and hits the resume on August 15. Within a few minutesAfter resuming, it will kick-start the report bursting on August 15 and continue with the next upcoming instances based on the given frequency.
You can retry failed burst schedules, pause, resume, or delete burst schedules.
...