3589392 - SAC Data Action - More than 5 min in Pending State

The job data action is in pending state for more than 5 min. Subsequent runs of this same data action have a pending state of around 1 sec.

SAP Analytics Cloud 1.0

• If multiple Data Actions are triggered simultaneously, they must wait for execution slots.
• On a public tenant, Data Actions from other customers may also impact queue times, as resources are shared.
• Long-running tasks (e.g., refreshing large reports) can consume system resources, delaying job execution.
• If a job is already running for the same user or version, any new job will remain pending until the previous one completes.
• If CPU, memory, or other required resources are fully utilized, new jobs must wait until resources become available.
• A high volume of jobs running simultaneously can extend pending times until the queue clears.   

Reviewing the scheduling approach, limiting unnecessary parallel executions, or checking overall tenant resource usage.

Data action, sac, pending state, CPU, memory, resources  , KBA , LOD-ANA-PL-DA , Data Actions , Problem