Escalation expiration

[deanhannigan]

Description

Escalation approval duration can now be configured along with an optional auto resolution strategy.

• Escalation Resolution - you can decide how your approvals end.
  • Expire the current default behaviour. When its time on the queue ends, it simply terminates
  • Accept request | Reject request - When its time on the queue ends, approve | reject the users request and resolve the escalation.
• [Enterprise] Introduced is the Never expire mode. When selected, the escalation approval will only ever leave the system if its resolved or cancelled by a user.
• [Enterprise] Custom - configure a completely bespoke duration in hours, days or weeks.

Addresses

• Request Expiration #19659

Screenshots

You can now choose the duration in the approval modal. Seen here, the full list of options available at the enterprise level. All options outlined in the attached issue.

Custom; hour, day and week duration. Only on the Enterprise tier.

License Expiry Flow. Newly raised escalations will cap on the server-side to the max allowed duration in the event of a downgrade. Escalation approvals already pending will remain pending, with the full duration with which they were created.

The resolution select. Expire will simply terminate the approval leaving the tool are resource untouched.

Launchcontrol

Add the ability to configure approval escalation duration and auto resolution behaviour.

---

Summary by cubic

Adds configurable expiration to agent approval policies, with presets, custom durations, "never expires," and automatic approval or rejection when a request expires. New escalations respect a per-plan duration cap, while existing approvals keep their original expiry.

• Adds approval expiration settings and expiry outcomes to the policy editor; omitting a duration means the policy never expires, so no expiry job is scheduled, and an outcome without a duration is rejected.
• Caps new escalation requests at the licensed duration, shows plan-limit warnings, and clears the warning when the expiry selection changes.
• Auto-expired approvals run the frozen tool call and complete the request, while auto-rejections mark the request rejected instead of timed out.
• Shows a fallback summary for policies that notify recipients without named approvers, using the provider type and channel target; "DM" appears only for Slack and Teams.
• Replaces escalation delay fields with optional duration values (seconds on policies, milliseconds on escalation docs); absence means the request never expires.
• Moves the Duration utility into shared-core so backend-core and the builder import it from one place.

^{Written for commit 4e2bf40. Summary will update on new commits.}

[deanhannigan]

@cubic-dev-ai review

[cubic-dev-ai]

@cubic-dev-ai review

@deanhannigan I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

All reported issues were addressed across 24 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 24 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 24 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>