3788251 - Only the first 20 Data Actions or Multi Actions started by executeInBackground() are executed, SAP analytics cloud

When using the executeInBackground() scripting API in an SAP Analytics Cloud Analytics Application (Story) to trigger multiple Data Actions or Multi Actions in rapid succession:

• Only the initial background executions are started.
• Additional executeInBackground() calls are not executed.
• Only the successfully started executions are displayed in the Data Action Job Monitor or Multi Action Job Monitor.
• No error message is displayed for the executions that were not started.

SAP Analytics Cloud

1. Open a story.
2. Call executeInBackground() repeatedly in a loop.
3. Execute the script.
4. Observe that only the first 20 executions are created.

This behavior is by design.

The executeInBackground() API is protected by an API rate limiting mechanism. The current implementation allows up to 20 API invocations within a rolling 60-second window. Once the limit is exceeded:

• Additional API calls are discarded.
• The corresponding Data Action or Multi Action executions are not started.
• Unsuccessful execution attempts are not visible in the corresponding Job Monitor.

The rate limiting mechanism is implemented to help protect system stability and performance, as Data Action and Multi Action executions consume backend processing resources and Job Queue Management (JQM) execution capacity.

Avoid triggering more than 20 executeInBackground() API calls within a rolling 60-second window.

• The executeInBackground() API is designed to protect backend processing resources through API rate limiting. If a business scenario requires a larger number of background executions, the scripting logic should be designed accordingly.
• SAP Analytics Cloud provides the Timer scripting object, which can be used to trigger delayed events in a story scripting. You may evaluate and test whether it is suitable for your scenario. For more information, refer to the SAP Help Portal – Timer scripting object. However, this approach has not been validated by SAP for this specific scenario. Please evaluate whether it is suitable for your own implementation.

SAP Help Portal – Timer scripting object

executeInBackground, data actions, background, rate limit, 20 calls, 60 seconds, job monitor, executions not visible, unified story scripting, api limit, throttling, batching, timer, planning, multi action , KBA , LOD-ANA-UNS-SCR , Unified Story Scripting related Issues , Problem