Repository navigation
fix(db): optimize Project backfill and repair archived workflows - #8962
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@cubic-dev-ai review this PR |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 4 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
|
|
@cubic-dev-ai review this PR |
@mzxchandra I have started the AI code review. It will take a few minutes to complete. |
There was a problem hiding this comment.
No issues found across 4 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.
Turn on auto-fix | Re-trigger cubic
Summary
Keep healthy Project backfill batches at 200 new-Project singletons or 50 existing-Project singletons; process fork families atomically. Remove elapsed-time batch shrinking and the pause after successful batches.
Bulk-load existing Project evidence with indexed membership lookups and combine timeout/validation queries to reduce database round trips.
Remove the outer 20-minute and 10,000-batch scheduling caps. Preserve transaction timeouts, bounded contention retries, authority/constraint guards, and resumable completion receipts for the existing migration.
Automatically archive workflows left active inside archived workspaces, disabling their dependent records in a bounded transaction. Preserve existing archive timestamps and the provider-cleanup guard.
Type of Change
Testing
Checklist