You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Trigger.dev and want to start contributing to the core platform. I'd like to fix #3726 — maxElapsed timeout boundary bypassed in ExponentialBackoff.execute (packages/core/src/v3/apps/backoff.ts).
The retry loop only enforces maxElapsed against the summed sleep delays in retryAsync, and never against the real wall-clock time execute() already tracks in elapsedMs (callback duration + sleeps). As a result, slow callbacks can run far past the configured maxElapsed budget.
I already have a small, tested fix ready (the loop breaks once elapsedMs >= maxElapsed * 1000), with unit tests covering the wall-clock cutoff, the success path, and the maxRetries path, plus a patch changeset for @trigger.dev/core. I'd love to be vouched so I can open the PR, and to keep contributing afterwards.
Activity
matt-aitken commentedon Oct 7, 2026
We have a new Vouch policy, please see the discussion here: #5010