The external HTTP data action keeps returning undefined for the customerTier field in the success output. Our Python backend service is definitely sending the correct JSON back. We’ve set the Architect mapping to $.response.data.tier, but the trace logs show the payload flattening correctly on the first hop. Here is what the endpoint sends when we test it:
{
"status": 200,
"data": {
"tier": "gold",
"accountId": "88219"
}
}
The Python SDK handles the token refresh without problems. We tried switching the JSON path to $.data.tier and $.tier, but Architect just drops the value entirely.
Error traces in the platform console only show MappingResult: undefined with no HTTP 5xx codes. It looks like the Data Action parser is choking on the nested object structure. We’ve been tweaking the success mapping expression for hours and nothing sticks. Does the JSON path resolver ignore the data wrapper by default, or is there a specific syntax we’re missing for nested payloads. The batch job is stuck waiting on this variable.