Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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. After 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.

Refer the following pages:

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.
 

Copyright © Intellect Design Arena Limited.

All rights reserved. These materials are confidential and proprietary to Intellect Design Arena Limited and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Intellect Design Arena Limited.