InfoSol Help Desk
How can we help you today?
Ability Kill Burst from Activity Log (Admin ONLY)
Bryan Baca
Hey Kirc. Thanks for the detail.
"Placing a 'Pause' and/or 'Kill' button/link with the running Bursts that only is shown when the ADMIN account is logged in, would help greatly, especially when there are hundreds of jobs running at the time. "
Within Monitor > Schedule > Schedule there is a Stop option. If the processing of the Burst is within InfoBurst control (i.e. an InfoBurst process), then the Burst will stop and no further processing will occur. If the Burst process is outside InfoBurst control (i.e. WebI refresh), then InfoBurst will issue a stop request to the processing system. InfoBurst cannot kill processes it does not control and there is no guarantee the stop request to the processing system will be fulfilled.
"..maybe the burst content can be diverted, to 'review hold' which will allow the job to complete with the option to send, if approved. (but this would have to be made available at run-time)"
Such a feature already exists. See the following article for details:
https://help.infosol.com/en/support/solutions/articles/19000118337-review
Kirc Breden
In BusinessObjects CMC > Instance Manager, a running job can be killed (deleted) without causing any other jobs to be interrupted.
Given this is a destructive method, to quickly prevent a publication/schedule from processing/sending content. There does not seem to be any, UI-based method to do the same in InfoBurst UI.
IBMaint.exe can stop ALL bursting, but that is a scattergun approach to a BB gun problem. Secondly, with new server hardening being implemented in increasing customer environments, accessing the desktop of the server, before the damage is done, cannot be accomplished quickly, as getting on a server can now take as much as 5 minutes of multiple steps of effort, just to log in.
Placing a 'Pause' and/or 'Kill' button/link with the running Bursts that only is shown when the ADMIN account is logged in, would help greatly, especially when there are hundreds of jobs running at the time.
Conversely, if killing a burst is not possible without great disruption, maybe the burst content can be diverted, to 'review hold' which will allow the job to complete with the option to send, if approved. (but this would have to be made available at run-time)