SSO Token Validation Failure During WFM Schedule Publish API Calls

Administration
1

My current config is completely failing…

We are experiencing a consistent 401 Unauthorized error when attempting to automate our weekly schedule publication via the WFM API. This is happening specifically during the high-volume publish window for our America/Chicago operations. The issue seems tied to the SSO token refresh mechanism within our integration layer.

Steps to reproduce:

  1. Generate a fresh access token using the Client Credentials flow.
  2. Call POST /api/v2/wfm/schedule/publications with the standard payload for a 7-day schedule block.
  3. Observe the immediate 401 response, even though the token validity window is confirmed active in the developer console.

The error payload indicates Invalid JWT signature. We have verified the client secret and ID are correct. This started after the last platform update. Is there a known issue with token validation latency or signature verification for WFM-specific endpoints? We need this resolved before Monday’s publish cycle. Any insights on token scope requirements for WFM automation would be appreciated.