René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"bug: useRealtimeRun onComplete fires prematurely in self-hosted environment (Traefik + Docker Compose)","articleBody":"### Provide environment information\n\n### Environment Information\n#### System:\n    OS: macOS 15.7\n    CPU: (36) x64 Intel(R) Xeon(R) W-2191B CPU @ 2.30GHz\n    Memory: 71.57 GB / 128.00 GB\n    Shell: 5.9 - /bin/zsh\n#### Binaries:\n    Node: 23.6.1 - /Users/\u003chome\u003e/.nvm/versions/node/v23.6.1/bin/node\n    npm: 10.9.2 - /Users/\u003chome\u003e/.nvm/versions/node/v23.6.1/bin/npm\n    pnpm: 10.19.0 - /Users/\u003chome\u003e/Library/pnpm/pnpm\n\n### Reproduction Environment\n- Hosting: Self-hosted using the standard Trigger.dev `docker-compose.yml`.\n- Reverse Proxy: Traefik.\n- Hook Config: Using `baseURL` pointing to the Traefik entrypoint for the Trigger API.\n- SDK Versions: `@trigger.dev/sdk@4.3.2`, `@trigger.dev/react-hooks@4.3.2`.\n- Framework: Next.js 16.10.0 / React 19.2.0\n\n### Infrastructure Details\nThe instance is running behind Traefik using the default Docker Compose setup. While the `onComplete` callback fires early, the `run` state returned by the hook _does_ continue to update correctly in the UI as the task progresses, eventually reaching `COMPLETED`. This suggests the realtime connection itself is working, but the logic governing the callback trigger is misfiring in this network environment.\n\n### Describe the bug\n\nWhen using the `useRealtimeRun` hook with a self-hosted Trigger.dev instance, the `onComplete` callback fires immediately upon the first successful data fetch, even if the run is still in an active state (e.g., `EXECUTING`).\n\n\n### Reproduction repo\n\nNone\n\n### To reproduce\n\n### Reproduction Steps\n1. Trigger a task that includes a significant delay (e.g., 5-10 seconds).\n2. Use `useRealtimeRun` in a client component with a `baseURL` and an `onComplete` callback.\n\n```ts\nconst { run } = useRealtimeRun(runId, {\n     accessToken: publicToken,\n     baseURL: \"https://your-self-hosted-trigger.com\",\n     onComplete: (run) =\u003e {\n       console.log(\"onComplete called with status:\", run.status);\n     }\n   });\n```\n\n3. Observe that onComplete is called almost immediately after the component mounts.\n4. Logging the `run` object inside `onComplete` shows `status: \"EXECUTING\"`.### Expected Behavior\n`onComplete` should only be called once the run reaches a terminal state (`COMPLETED`, `FAILED`, `CANCELED`, `CRASHED`).\n### Actual Behavior\n`onComplete` is called immediately with the non-terminal state.\n\n### Additional information\n\nI also checked traefik logs but there were no issues.","author":{"url":"https://github.com/bbreunig","@type":"Person","name":"bbreunig"},"datePublished":"2026-01-09T10:16:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/2856/trigger.dev/issues/2856"}