bug: Self-Hosted: Runs Page Shows No Run History (Bug Started Today, Even After Fresh Deploy)

[atul7017128880]

Provide environment information

pc info

System:
OS: Windows 11 10.0.26100
CPU: (28) x64 Intel(R) Core(TM) i7-14700HX
Memory: 7.09 GB / 31.78 GB
Binaries:
Node: 22.15.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.21 - C:\Users\atul7\AppData\Roaming\npm\yarn.CMD
npm: 10.9.2 - C:\Program Files\nodejs\npm.CMD
pnpm: 10.9.0 - C:\Users\atul7\AppData\Local\pnpm\pnpm.EXE
bun: 1.2.10 - C:\Users\atul7.bun\bin\bun.EXE

Describe the bug

The Runs page in the self-hosted Trigger.dev dashboard no longer shows any run history.
This issue started today and persists even after a full clean redeploy.

• Redeployed all containers
• Pulled the latest Trigger.dev images
• Deleted all data (database + ClickHouse)
• Started everything from scratch
• The Runs list is still empty

Expected Behavior
The Runs page should display a list of executed runs for workflows.

Actual Behavior

• Runs page loads but no runs appear
• Workflows execute normally in the background
• No run history is visible

Notes

• This issue did NOT occur yesterday

Reproduction repo

.

To reproduce

.

Additional information

No response

[FerasAloudah]

Did you manage to fix this? Currently facing the same issue.

[tomaisthorpe]

@FerasAloudah , I had the same issue. There's some kind of race condition with the migrations in ClickHouse which prevents the run list working, you'll probably see some errors there if you check the logs.

Restart ClickHouse and then it should be work.

Spoke too soon, the migrations worked, but runs only appear if ClickHouse isn't actually running.

[tomaisthorpe]

Found the issue. It's most likely due to permission issues on your postgres user where it's not able to create a replication slot. The logs that show this are debug logs so aren't shown by default, you can able them on the helm chart here.

I also saw some logs in my postgres cluster to help diagnose it.

[FerasAloudah]

Found the issue. It's most likely due to permission issues on your postgres user where it's not able to create a replication slot. The logs that show this are debug logs so aren't shown by default, you can able them on the helm chart here.

I also saw some logs in my postgres cluster to help diagnose it.

Hi Tom, just saw this. Thanks a lot this actually helped me solve the issue. There was indeed a role issue with the DB user.
Also, searching the webapp logs for this emoji 🗃️, helped in getting some useful logs for why this wasn't working.

[gautamsi]

This helped me - rybbit-io/rybbit#559 (comment)
Seems like there was problem with my proxmox vm configuration for CPU type