Setting up a Data Action to pull live SIP registration counts from our legacy carrier gateway. Endpoint returns a 200 with the expected JSON, but the parser keeps choking on it. Flow ID f4a2b8c1-99e3-4d2a-b1c0-77e8f9a2d411 in US1. Logs show the request goes out with the correct API key. The carrier wraps the payload in a {"results": [...]} object. Mapped the response path to $.results[0].reg_count in the Data Action config. Console throws Data Action execution failed: Invalid response format. Expected object, got array. even though the path resolves fine in Postman. Tried switching the content type to text/plain. Don’t see any change. Architect just drops the call to the fallback queue. Carrier side shows the SIP trunks are fully registered, so it’s not a network hiccup. Can’t get past the Set Data step. Response mapping seems completely busted for nested arrays.