3797773 - import data job fails with "data mapping ended unexpectedly" after upgrade due to oauth failure on odata connection – sap analytics cloud

• Import job fails with the message "Data mapping ended unexpectedly."
• Newly created import jobs hang and cannot proceed from query selection/mapping; the screen does not advance.
• Newly created import model with same steps works fine.

• SAP Analytics Cloud 2026.15.6 

1. Open the target import model and start the existing import job.
2. Observe that the job terminates with "Data mapping ended unexpectedly."
3. Create a new import job using the same OData connection.
4. Select the source/query and proceed; the workflow hangs and does not move to the mapping step.

The issue is currently under investigation of development team.

The issue is currently under investigation of development team.

• Refer to: How to collect a HTTP archive (HAR) file and Console Log file in SAP Analytics Cloud
• Refer to: [Best Practice] How to capture the OData query when using import data connection
• Refer to: Unable to run a specific import job of a model in SAP Analytics Cloud (SAC)
• Refer to: Unexpected termination of data load for data models in SAP Analytics Cloud

sac, import data, data mapping ended unexpectedly, odata, oauth, authentication_error, error_invalid_auth_request, 502 bad gateway, gather stage, datasphere, odata connection validation, mapping hangs, import job failure, data acquisition, sac upgrade , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem