Handling failed budget template processing: Requeue and Recovery

When a budget template processing job like Activate, Process Pending, or Clear Local Budget Copy fails, the template can remain in Processing status. In this situation, use the Recover After Processing Error action to reset the template to Not Ready.

This recovery action is available only when the template is in Processing status and must be used only if a processing job has failed and cannot be successfully requeued.

Recovery always resets the template to Not Ready, regardless of its previous state. All budget groups and totals are deleted and must be regenerated through full re activation.

Caution: If multiple templates on the same scenario are processing, you must wait for the other templates to complete before proceeding.

The table below provides a summary of the steps required to safely recover a template after a job failure during processing. The recovery process includes requeuing the failed job, removing any associated async requests and triggers when necessary, recovering the template, and reactivating the template after the root cause has been resolved. Performing these steps helps minimize processing conflicts and maintain data consistency during template recovery.


Step	Process	Description
1	Attempt to requeue the failed job	Review the failed job, resolve any identified issues, and requeue the job. The Application Administrator role is required to requeue a failed budget template job. See Requeuing a failed job.
2	Verify the requeued job status	Monitor the requeued job. If it completes successfully, allow the remaining jobs to finish automatically. No further action is required once the template reaches Ready status. See Requeuing a failed job. If requeuing is unsuccessful, proceed to step 3.
3	Perform cleanup if requeuing fails	Delete all async requests and triggers associated with the failed job. The Application Administrator role is required to requeue a failed budget template job. Use Deleting async requests and triggers for the failed cube refresh for cube refresh failures. Use Deleting async requests and triggers for all other failed jobs for all other job types. Important: Ensure all async requests and triggers related to the failed job are completely removed before proceeding with template recovery to prevent processing conflicts and potential data inconsistencies.
4	Confirm cleanup is complete	Verify that all pending async requests and triggers related to the failed job have been removed. Repeat Step 3 for all failed jobs within the template until all failed job async triggers and requests have been cleaned up.
5	Recover the template	Run Recover After Processing Error to reset the template from Processing status to Not Ready status. See Recovering the template.
6	Resolve the root cause and reactivate the template	Resolve the underlying cause of the failure and reactivate the template. See Activating budget templates. See Activating templates with selective budget groups.