SAC Calendar – Automatic Data Locking Task Remains “In Progress” After Preceding General Task Is Sub

[#1]

Hi SAP Community, We are facing an issue with SAP Analytics Cloud Calendar – dependent/automatic Data Locking tasks. The scenario is as follows: We have created a Calendar Process with the following sequence: General Task → Lock After General Task (Automatic Data Locking Task). The Data Locking task is configured to lock the required entity after the preceding General Task is successfully submitted. The expected behavior is that, once the General Task is submitted successfully, the dependent Data Locking task should start automatically and apply the configured lock. Previously, the exact same configuration was working perfectly. After the General Task was submitted, the Data Locking task was triggered and the entity was locked as expected. However, during our recent testing in Production, the preceding General Task was submitted successfully, but the dependent “Lock the Entity” task remains “In Progress” and does not proceed to the expected status. This behavior was not observed earlier when the same configuration was tested. As an additional test, we created and executed the Data Locking task independently, without the dependency on the preceding General Task. In that scenario, the data locking worked successfully. Therefore, the issue appears to be specifically related to the dependency/triggering of the automatic Data Locking task after completion of the preceding General Task, rather than the underlying data-locking configuration itself. Expected behavior: After the preceding General Task reaches Successful/Completed status, the dependent Data Locking task should automatically start and apply the configured lock. Actual behavior: The preceding General Task is completed successfully, but the dependent Data Locking task remains In Progress and does not execute/complete. Whether there has been any recent change, update, or known issue in SAC Calendar/Calendar Wizard dependency handling or automatic Data Locking that could cause this behavior? I would also appreciate your guidance on whether there are any additional configuration, authorization, data-locking ownership, or security requirements that need to be checked specifically for dependent automatic Data Locking tasks. Note: The standalone Data Locking task works successfully, and the same dependent configuration was working correctly during our earlier testing. Thank you.