Conversation
…timeout ## Problem Evidence export times out and fails to complete in-browser for orgs with large automation volume or output size. Both export variants (with and without JSON) fail with no file downloaded. ## Root cause The `export-organization-evidence` Trigger.dev task has `maxDuration` capped at 30 minutes. For orgs with high task counts and large evidence archives, the export generation exceeds this ceiling, the task is killed before completing, and the frontend receives a failure response with no download link. ## Fix Raise `maxDuration` from 30 minutes to 60 minutes in the trigger task config, matching the realtime SDK token TTL (1h) and other heavy org tasks like `run-org-integration-checks`. Also enable one retry attempt to handle transient failures. This is a localized change in `apps/api` trigger configuration with no impact on other systems. ## Explicitly NOT touched - Frontend UI or export button logic - Task queueing or retry storm prevention (already hardened in prior work) - OOM or proxy timeout handling - Evidence storage or generation logic ## Verification ✅ Task duration config updated to 60*60 seconds ✅ Retry maxAttempts set to 1 ✅ Tested with high-volume org evidence export completes within new ceiling ✅ Export download available in-browser on success
…ort-timeout fix(evidence-export): raise trigger task duration ceiling to prevent timeout
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
|
🎉 This PR is included in version 3.95.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.
Summary by cubic
Increase the
exportOrganizationEvidenceTaskmax compute time to 60 minutes to prevent timeouts on large org evidence exports. Adds a regression test to lock the new ceiling.maxDurationfrom 30m to 60m so large ZIP streams can finish before Trigger.dev kills the run.maxDurationis at least 1h and under 24h to prevent misconfiguration.Written for commit 1d44d64. Summary will update on new commits.