Trying to understand why my Architect Data Action fails when mapping a nested JSON response from an external REST API. I have configured a Data Action to call our internal identity service at https://api.internal.example.com/v2/user/details. The request uses a Bearer token fetched from a separate Vault integration step, which works correctly as confirmed by successful 200 OK responses in the debug logs. The external API returns a JSON payload with the structure { "status": "success", "data": { "userId": "12345", "role": "agent" } }. My goal is to extract data.userId into the Architect variable user_id and data.role into user_role. I am using the standard JSON path syntax in the response mapping configuration: $.data.userId and $.data.role. However, the Data Action consistently fails with an HTTP 500 Internal Server Error on the Genesys Cloud side, and the error message in the Architect flow log simply states “Data action execution failed” without providing details on the mapping error. I have verified that the external endpoint is accessible and returns valid JSON. I have also tried simplifying the response to a flat structure { "userId": "12345" } and mapping $.userId, which works perfectly. This suggests the issue is specifically with navigating nested objects in the response mapping. I have checked the Genesys Cloud documentation for Data Actions, but it lacks specific examples for deep object traversal. Is there a limitation on the depth of JSON paths supported in Architect Data Action response mappings, or is there a specific syntax requirement for nested objects that I am missing? I need to confirm if $.data.userId is the correct syntax or if a different accessor is required for nested fields in this context.