bug: Task run page, main span doesn't refresh on finished task

[0ski]

Provide environment information

Dashboard page

Describe the bug

Main task run span doesn't come to the end

Reproduction repo

https://github.com/triggerdotdev/trigger.dev

To reproduce

• Create a test run
• Go to its page when it's running
• Wait till it is finished
• Refreshing the page helps

Additional information

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• bug: [v4] batch completed does not reflect in parent task run #1958

Related Issues

• bug: no run logs and metadata in dev mode with bun runtime #1671
• [v3] Self-hosted runs not completing #1668
• bug: Run task history not showing after upgrading from beta-20 to beta-25 #2326
• bug: Self-Hosted: Runs Page Shows No Run History (Bug Started Today, Even After Fresh Deploy) #2726

👤 Suggested Assignees

• cachho
• terion-name
• rharkor
• MattCarneiro
• atul7017128880

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[ShubhaamTiwary]

I can take this. Are you open to a community PR for this issue?

[bharathkumar39293]

Hi everyone,

The issue with the main task run span not refreshing on finished tasks has been addressed in PR #2875

This fix reconciles Postgres’ authoritative run lifecycle with potentially lagging ClickHouse telemetry at the UI layer only, ensuring the root span status and duration update immediately when a run finishes.

Once this PR is merged, the task run page should correctly show the completed span without needing a manual refresh.