Architect Get Schedule Node 404 on Published Agent

Anyone know why the Get Schedule node returns a 404 error for agents whose schedules were published successfully via the WFM API yesterday? The flow is deployed, the agent IDs are correct, and the schedule is active in the Chicago timezone, yet the node fails to retrieve availability data for every single call.