chore(trigger): upsize task size - #6007

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jul 28, 2026 5:35pm

PR Summary

Medium Risk
Infra scaling changes affect core workflow/schedule execution and fork copy reliability/cost; UI changes are localized with new tests.

Overview
Upsizes several Trigger.dev background tasks to handle heavier workloads: fork-content-copy and knowledge-connector-sync use large-2x, while schedule-execution and workflow-execution move to medium-2x. fork-content-copy documents why the larger machine matters (in-memory copy of rows, KB chunks, embeddings, blobs; single attempt so OOM is not retried).

Fork activity event badges get hover tooltips for non-success states (Queued, In progress, failure reason, partial-copy warnings); successful completed rows stay tooltip-free.

Activity log rows without expandable details render as a plain div instead of a disabled button, so badge/cell tooltips still receive pointer events.

^{Reviewed by Cursor Bugbot for commit fbe8971. Configure here.}

Greptile Summary

Upsizes Trigger.dev machine presets for heavier background work and fixes fork/activity-log badge hover tooltips on non-expandable rows.

• workflow-execution and schedule-execution move from medium-1x to medium-2x
• knowledge-connector-sync and new fork-content-copy use large-2x
• Activity log renders non-expandable rows as plain divs so nested hover tooltips work
• Fork activity panel adds status tooltips on Event badges, with unit coverage

Confidence Score: 5/5

Safe to merge; machine preset upsizes use valid Trigger.dev sizes and the activity-row/tooltip changes are covered by focused tests.

Diff only increases known machine presets and fixes pointer-event swallowing for tooltips on inert activity rows, with matching unit tests and no contract or security surface changes.

_{Reviews (1): Last reviewed commit: "chore(trigger): upsize tasks" | Re-trigger Greptile}