Need some help troubleshooting… a 500 Internal Server Error when the POST /api/v2/recordings/screen endpoint is triggered by our weekly schedule publishing webhook. This happens specifically during peak load in the Chicago timezone (CT). The Architect flow uses the standard WFM integration module. Any insights on whether this is a known throttling issue or a payload format mismatch? Environment: Genesys Cloud v12.5, US East.
Check your webhook payload structure for the screen recording trigger; the 500 error usually stems from malformed JSON when the Architect flow passes undefined variables during peak load.
Warning: Verify that the recording_id field is not null before the POST request executes.