Applies to Product - FnO Platform
What’s happening?
Customers are experiencing errors with batch jobs, including access denied errors, partial success statuses, and jobs being jammed or stuck in execution status without progressing.
Reason:
This are caused by various factors, including access permissions, batch job configurations, and high resource consumption leading to throttling of batch jobs.
Resolution:
- For access denied errors, ensure that the batch job has the necessary permissions to execute. If the job fails due to access issues, consider raising an incident for further assistance to Authorization Team , Please note Batch Team don't own this issue.
- If a batch job is partially successful and does not finish processing, review the job's configuration and any related error messages in Batch log to identify the cause.
- In cases where the batch server is jammed, cancel any stuck batch jobs to free up resources. It may also be necessary to adjust the number of batch server threads to optimize performance.
- Monitor the execution of batch jobs to avoid generating a large number of tasks during business hours, which can lead to high resource consumption and throttling.
- If issue is happening only with single batch job then please check the className and redirect to Job Owning Team for further investigation.
- Customer should investigate on their own if its custom class .
- Check if tasks are complete but Batch jobs are still stuck in execution then redirect to Batch Team for the cause of it and RCA.