Improved
OnSched API 3.24.3 — Faster v1 alias timeouts
about 2 hours ago by ReadMe GitHub Action
V1 alias endpoints
/consumer/v1 and /setup/v1 still confirm the caller’s v1 token against live v1 (not JWT expiry alone). That check is cached for a short window.
Internal token validation, Lazy Hydration calls to v1, and the shim’s /v3 hop on the same request now share a time budget. If that budget is used up, the alias response is 500 with V1 alias request timed out instead of hanging until the client gives up.
Availability SQL on GET …/availability/… is unchanged.