How do I properly configure the screen recording data pull for our coaching dashboard without triggering constant authentication blocks? The external coaching platform we brought in last month keeps failing to fetch agent desktop captures. Platform API version 2.2 is what the vendor documentation points to, and the endpoint in question is /api/v2/recordings/screen. Every time the scheduled job runs at 08:30 PT, the integration dashboard flashes a 403 Forbidden response. Management already flagged the training team because three supervisors missed their mandatory calibration reviews last week. The vendor support ticket just says the OAuth scope needs updating, but the org admin locked down the tenant permissions after the data breach scare in November. My supervisor role only shows monitoring tabs, so the API credentials panel stays completely grayed out in the admin console. Queue metrics look normal, but the screen capture queue sits at zero processed items. Tried clearing the browser cache and switching to a private window, doing jack all. The error payload returns something about insufficient client permissions on the recording_resource type. Not sure if this ties into the new compliance recording settings we toggled last Tuesday. Console logs point to a token expiry mismatch, but the refresh interval is set to thirty minutes. The environment runs on the us-west-2 region cluster, and the tenant ID matches what the integration guide expects. We can’t just hand out admin access to fix this. The webhook payload keeps failing validation at the signature check step. Error trace shows a null pointer exception on the media_url field when the system tries to parse the recording metadata.