I’ve spent hours trying to figure out why the Parse JSON block in our custom Architect flow consistently fails with a 400 Bad Request status code when invoked via the Platform API from our AppFoundry-hosted widget, specifically during the multi-org OAuth handshake sequence. The integration is designed to synchronize customer context data between our premium application and the Genesys Cloud contact center, but the payload structure appears to be rejected by the platform’s internal validation layer despite adhering to the documented schema requirements. We are deploying this solution across multiple organizations in the America/Los_Angeles timezone, and the issue manifests only when the X-Genesys-PR-Capacity header is omitted or when the request originates from the secondary tenant environment. The error response body returns a generic Invalid JSON structure message without specifying the exact field causing the failure, which makes debugging exceptionally difficult given the nested object hierarchy involved. We have verified that the Content-Type header is set to application/json and that the payload size remains well within the 64KB limit for Data Actions. Additionally, we have enabled verbose logging in the Architect flow, but the logs only indicate a generic execution_error without providing insight into the parsing logic. The SDK version used for the frontend component is 2.14.0, and the backend service utilizes the genesys-cloud-purecloud-sdk-node version 2.68.0. We suspect this might be related to how the platform handles special characters in the customer_id field when passed through the OAuth token exchange process, but we need confirmation on whether this is a known limitation or a configuration issue within our AppFoundry deployment. Any insights into the specific validation rules applied during the JSON parsing phase in multi-tenant environments would be greatly appreciated, as we are currently unable to proceed with the production rollout due to this persistent integration failure.