When a report bursting is scheduled, it acts as normal 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 it was paused, which means that any reports that were in the queue to be generated, distributed, or processed would be is halted. If it report bursting is resumed, it fires once for the missed schedules after the resume once and continues with the next upcoming instances based on the given frequency. Let us take a scenario where a user pauses the report bursting For example, when a report bursting is paused on August 1 and hits the resume resumed on August 15. After resuming, it will kick-start starts the report bursting on August 15 and continue continues with the next upcoming instances based on the given frequency.
...