Does anyone know why a valid OAuth token with wfm:schedule:write scope returns a 403 Forbidden when attempting to create WFM schedules? The integration works in sandbox but fails in production. Verified the org ID matches. Checking the audit logs shows no specific denial reason. Is there a hidden permission level or a known issue with AppFoundry tokens accessing WFM endpoints directly?
1 Like