BYOC Edge WFM Data Action Failing with 403 During Schedule Publish

Quick question, has anyone seen this weird error? with our BYOC Edge deployment when trying to pull real-time schedule adherence data via a custom Data Action. The integration works perfectly in the staging environment, but production returns a 403 Forbidden error specifically during the weekly schedule publish window on Friday afternoons (CST). The error message indicates InvalidScope: WFM_SCHEDULE_READ is missing, yet the OAuth credentials attached to the BYOC app definitely include this scope. We have verified the token refresh cycle, and the access token is valid for another 45 minutes. It seems like the WFM API gateway is rejecting requests when the schedule lock is active, even for read-only endpoints. Has anyone else seen scope validation fail intermittently during high-load publishing events? We are using the latest Genesys Cloud SDK version 2.14.0 for our Node.js connector. The API endpoint being called is /api/v2/wfm/schedules/published. We need this data for our custom adherence dashboard, and the outage is causing significant reporting gaps for our shift supervisors. Any insights into whether this is a known limitation of BYOC Edge permissions during schedule transitions?