The forecasted shrinkage numbers keep jumping around in the WFM console, and the /api/v2/wfm/schedules endpoint throws a 400 INVALID_SCHEDULE_STRUCTURE error when I push the payload. I read that community thread about bulk imports, but the JSON schema still feels completely wrong for our twenty-agent environment since I don’t know how to set up forecasting, adherence, and shift swaps all at once. The documentation uses a deprecated timeZoneId format that breaks the validator, and it’s throwing off the sync.