Trying to get our configuration set up for a custom Data Action that authenticates against a third-party CRM using the OAuth 2.0 Client Credentials flow. The integration is deployed via the AppFoundry partner ecosystem and requires fetching user context from a secondary Genesys Cloud organization linked through multi-org capabilities. When the Data Action executes within an Architect flow, the initial token exchange succeeds, but the subsequent GET request to the CRM endpoint returns an HTTP 403 Forbidden error. The request headers include the Authorization Bearer token, Content-Type application/json, and the required X-Genesys-Cloud-Request-Id. Debugging logs indicate that the token validity period is sufficient, and manual cURL tests with the same token succeed outside the platform. The issue appears specific to the Data Action execution context, possibly related to how the platform handles outbound SSL pinning or IP whitelisting for partner integrations. The environment is running Genesys Cloud US-East with API version v2. Any insights into whether the Data Action runtime imposes additional network restrictions or header stripping that might cause this 403 response?