[FEATURE] Rescue from 4xx AND 5xx so actions can be retried later

Resolved 💬 3 comments Opened Mar 28, 2026 by ruyrocha Closed Mar 28, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Currently I'm working on an environment that for any outrageous reason the my token expires after certain time, the server responds with 400s OR 500s.

I wish it was possible to recover and retry the requests later, instead of dropping them right away, so I can properly continue with my work.

Proposed Solution

Not being able to retry the requests later - 400s specifically - is a big deal breaker, since all progress is lost; when API responds with 400s OR 500, the request should not be lost.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

API and model interactions

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗