Anyone know why the /api/v2/messaging/conversations endpoint returns 403 Forbidden when triggered from an architect flow? we are using the latest sdk but the token seems valid. the error happens only for specific orgs in our multi-tenant appfoundry setup. no clear logs on the gen side. is it a rate limit issue or permissions? the integration works fine via postman but fails in production flows.
Make sure you verify the service account permissions in Architect. It’s often not a rate limit issue but missing messaging:conversation:read scope on the integration user. Check the token payload in JMeter to confirm scopes match the API requirements. Sometimes the SDK handles auth differently than raw HTTP calls, causing silent failures in flows.