How come this setting causes a 403 Forbidden error when invoking an external API action? We are deploying a premium AppFoundry integration for a PST-based client. The flow uses a valid OAuth token with full platform permissions, yet the external API call fails immediately upon execution.
The error logs indicate a permissions mismatch despite correct scoping. We have verified the token validity and endpoint accessibility. Any insights on handling cross-org API calls within Architect flows would be appreciated.