Production hardening: error recovery, call monitoring, alerts #18

New issue

Open

opened 2026-04-05 21:36:57 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-04-05 21:36:57 -07:00

Owner

Make Osprey reliable enough for real users with high-stakes calls.

Deliverables

Retry + backoff on Twilio API failures
Graceful degradation: if bridge fails, SMS the user with a callback number
Call monitoring: detect if a call drops unexpectedly mid-queue, auto-retry
Uptime Kuma health check endpoint integration (cf-monitoring stack already running)
Alert on repeated rejections (IVR sequence may have changed)
Call logs retention policy: 30 days default

Make Osprey reliable enough for real users with high-stakes calls. ## Deliverables - Retry + backoff on Twilio API failures - Graceful degradation: if bridge fails, SMS the user with a callback number - Call monitoring: detect if a call drops unexpectedly mid-queue, auto-retry - Uptime Kuma health check endpoint integration (cf-monitoring stack already running) - Alert on repeated rejections (IVR sequence may have changed) - Call logs retention policy: 30 days default

pyr0ball added this to the Public Launch milestone 2026-04-05 21:36:57 -07:00

No labels

backlog

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: Circuit-Forge/osprey#18

No description provided.