bug: GitHub App preview deployments intermittently fail with internal errors; check conclusion can contradict actual deployment status

[Octember]

Summary

Since around 2026-06-09/10, GitHub App–initiated preview deployments for our Trigger Cloud project proj_pnreuadgcfkartotfwml (preview environment, per-PR branches) have been failing intermittently — roughly half or more of pushes — with generic internal errors. Successes are interleaved with failures on identical code, so this does not look like a problem with our build.

Failure shapes observed

1. Fast internal failure (check completes in ~6–60s, too fast for a real build):

Status: Failed (Build failed)
Error: Something went wrong while progressing the deployment, please try again shortly. If you are seeing this error consistently, please reach out to us.

Example deployments: h6gmbayy, uqli4nzf, dp1p9v0m, siu1o8vl, vlnrnr1a, qqxgvf1q

2. ~3-minute failure pointing at build logs:

Status: Failed (Deployment failed)
Error: Deployment failed, please check the build logs for more details.

Example deployments: sy4f3jsh, 4d29op07, 0l2labd2

3. Failure with no version / no deployment link at all (the GitHub check run carries no deployment URL, and the deployment doesn't appear in the project's deployment list).

4. Status mismatch — deployment succeeded but the GitHub check reports failure:
Deployment g4rk7h7y (v20260610.2) shows as DEPLOYED in the deployments API/dashboard, but the GitHub check run for it concluded failure with "Deployment failed, please check the build logs for more details." (completed 2026-06-10T19:16:18Z, deployment finished 2026-06-10T19:16:17Z). A CLI-initiated deploy of the same commit (9jee6c6n, v20260610.3) succeeded concurrently.

Additional failed deployment IDs from earlier on 2026-06-10: cft5o8bb, lv3lt50n, wkoybpqp.

Expected

GitHub App preview deployments either build/deploy reliably, or surface a real, actionable error — and the GitHub check conclusion should match the deployment's actual final status.

Context

• Trigger Cloud (cloud.trigger.dev), project proj_pnreuadgcfkartotfwml, preview environment with per-PR branch deploys via the GitHub App integration.
• Monorepo (bun workspaces), private repo. CLI-driven deploys of the same commits (via trigger.dev deploy from CI) succeed reliably; only the GitHub App–initiated builds are flaky.
• We're aware we can disable the GitHub App preview-deploy toggle (and likely will), but reporting since the error text says to reach out if seen consistently — and the success-marked-as-failure case (g4rk7h7y) looks like a genuine bug in the integration's check reporting.

Environment

Cloud product issue (no local repro). Deploys initiated by the Trigger.dev GitHub App from GitHub pushes, not from a local environment.