The following issue is observed where jobs in SAP have already ended, while in the Automation Engine (AE) the associated jobs do not end.
In most cases, direct intervention is necessary to keep the workflow running.
If not intervened, the jobs usually end hours later and thus delay further processes.
This Error occurs in combination with high load periods, thus a connection to the workload is very likely). Jobs using R3_ACTIVATE_REPORT with Child Jobs are affected.
It looks like the Child Jobs are the reason why the delay occurs. As this has happened before, (v11.2.0) and we advised to update to v11.2.4. where the issue was resolved. The Automation Engine now has version 11.2.6 and the SAP Agent version 11.2.5. unfortunately the issue still occurs.
How the Agent works:
Release: 11.x /12.x
Cause type: Configuration
Root Cause: We can confirm that the root cause of the delay is huge job logs.
The reason for the delayed completion is the amount of job log lines being transferred.
The agent uses only one thread per job which is by design, this includes all child jobs.
When a very high number of job log lines is transmitted, there is a delay.
The following options are available for rectification or mitigation: