fix: say why Polar refused an activation #1

Merged
jwarykowski merged 2 commits from fix/polar-detail into main 2026-10-14 13:09:02 +00:00
Owner

Polar answers 403 for four reasons: the activation limit is reached, the key expired, the key was revoked, or the benefit has no activation limit set. The Worker sent the "maximum number of machines" message for all four. It now reads Polar's detail, gives each reason its own message, and logs it (wrangler tail).

Also turns on Workers Logs (observability) for both environments, so those log lines are kept and searchable in the Cloudflare dashboard, not only visible live in wrangler tail.

Polar answers 403 for four reasons: the activation limit is reached, the key expired, the key was revoked, or the benefit has no activation limit set. The Worker sent the "maximum number of machines" message for all four. It now reads Polar's `detail`, gives each reason its own message, and logs it (`wrangler tail`). Also turns on Workers Logs (`observability`) for both environments, so those log lines are kept and searchable in the Cloudflare dashboard, not only visible live in `wrangler tail`.
fix: say why Polar refused an activation
All checks were successful
CI / go (pull_request) Successful in 39s
CI / worker (pull_request) Successful in 31s
535b355a04
Polar's 403 covers a full key, an expired or revoked one, and a benefit without an activation limit; each now gets its own message, and the Worker logs Polar's reason.
feat: keep the Worker's logs in Workers Logs
All checks were successful
CI / go (pull_request) Successful in 43s
CI / worker (pull_request) Successful in 27s
6c6a2c3e7b
jwarykowski deleted branch fix/polar-detail 2026-10-14 13:09:02 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jwarykowski/licence!1
No description provided.