Why does this setting for screen recording retention cause immediate 403 Forbidden errors when the JMeter script attempts to start a session via the API? We are running a load test with 50 concurrent virtual agents using the Genesys Cloud Engagement API. The environment is a sandbox org configured for performance testing. When the retention policy is set to the default 30 days, the POST request to /api/v2/interactions/screen-recording/sessions returns a 201 Created status successfully. However, changing the organization setting to retain recordings for only 7 days triggers the failure.
The error payload returned is {"errors":[{"code":"Forbidden","message":"You do not have permission to perform this action."}]. The API key used in the JMeter test has the screen_recording:write and screen_recording:read scopes granted. We verified the token is valid by calling the /api/v2/interactions/screen-recording/settings endpoint, which returns the current configuration without issue. The failure happens consistently at the moment the session initiation request is sent.
We are using Genesys Cloud release 24.10. The load test script uses a simple HTTP Request sampler with the Authorization header set to Bearer <token>. The user profile assigned to the API key is a standard Agent profile with the Screen Recording capability enabled. We have tried resetting the API credentials and regenerating the token, but the 403 error persists as soon as the shorter retention period is active in the Admin UI.
Is there a known dependency between the retention policy duration and the API permissions for session creation? We need to validate if this is a bug in the API gateway or a configuration requirement we are missing. The concurrent load is low, so rate limiting is not a factor here. Any insight into why the retention setting would impact write permissions would be helpful.