Hermes Agent 92095ff5d6 fix: release reserved L2 agent when AMI redirect fails during escalation ...

Found during production smoke test: if the AMI Redirect call in
create_escalation() raises (channel gone, AMI hiccup), the agent stays
RESERVED forever with no owning call — orphaned out of the pool until
someone fixes it by hand. Now releases the agent and marks the
escalation failed before re-raising as a 502.

2026-08-29 14:01:40 +05:00

..

ami.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

app.py

feat: L1->L2 agent pool and routing engine for voice escalation

2026-08-28 16:22:32 +05:00

bridge_processing.py

feat: L1->L2 agent pool and routing engine for voice escalation

2026-08-28 16:22:32 +05:00

call_control.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

config.py

feat: L1->L2 agent pool and routing engine for voice escalation

2026-08-28 16:22:32 +05:00

http_client.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

ivr_fastagi.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

presenters.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

reconcile.py

.

2026-04-05 20:26:46 +05:00

recording_io.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

routes.py

feat: L1->L2 agent pool and routing engine for voice escalation

2026-08-28 16:22:32 +05:00

runtime.py

Initial import with GitLab CI/CD and registry deploy flow

2026-04-02 17:05:45 +05:00

voice_ai.py

fix: release reserved L2 agent when AMI redirect fails during escalation

2026-08-29 14:01:40 +05:00