3759945 - Error retrieving data locks due to excessive team assignment - SAP analytics cloud

• “Upload to model has failed unexpectedly. Error code: 5028” during file import from a story action to a planning model.
• “Import to model has failed while updating the dimension members. Error code: 5021” appears in logs/audit.
• When opening a story or input task with data locking enabled: “An error occurred while retrieving the data locks for the visible cells.”
• Browser developer tools may show: “You are not authorized to Read Data Locking.”
• User may also see the error "Execution of algorithm failed: SQL execution of prepared statement failed with error 293: argument type mismatch: invalid value(wrong argument) error returned from substr_regex"
• Error can be reproduced by a few specific users while many other users with the same roles/teams are unaffected.

• Product: SAP Analytics Cloud
• Data Locking

1. Error can be seen when running an import job.
2. Error also occurs when attempting to enter data into a planning enabled table.
3. There may be other use cases where this failure can occur if the data locks need to be evaluated.
4. In the model’s Data Management monitor, observe that the job ends with “Upload to model has failed unexpectedly. Error code: 5028.”
5. In the Chrome developer tools in the network tab you may see the error: "Execution of algorithm failed: SQL execution of prepared statement failed with error 293: argument type mismatch: invalid value(wrong argument) error returned from substr_regex"

A backend failure in data locking ownership evaluation is caused by users belonging to a very large number of teams; the excessive team memberships lead to oversized rule evaluation (for example, an overly large regular expression) and the process fails, surfacing as errors 5028/5021 during import and as data lock retrieval errors in stories.

1. Reduce the number of actively used teams:
2. Clean up and remove redundant teams to keep team count at a manageable level.
3. As a short-term workaround to unblock planning operations:
   1. Disable Data Locking Ownership for the affected ownership dimension in the model, or
   2. Temporarily disable Data Locking in the model.
4. Consider simplifying authorizations to avoid per-object team proliferation (for example, assign users directly via Data Access Control where feasible) to prevent future scalability issues.
5. Ensure roles assigned to affected users include at least Read permission on Data Locking to avoid the “retrieving data locks” error in stories.
6. Note: An improvement to mitigate this limitation is planned as a feature extension; no committed delivery timeline is available at this time.

• refer to: "An error occurred while retrieving the data locks for the visible cells" occurs when opening a story

error 5028, error 5021, upload to model failed, import job fails, planning model, data locking, data locking ownership, too many teams, team membership limit, file import, story action, unauthorized read data locking, visible cells, ownership dimension, scalability issues,error returned from substr_regex, error 293: argument type mismatch , KBA , LOD-ANA-PL-DLK , Data Locking , LOD-ANA-PL-DE , Data Entry and Mass Data Entry , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem