Hello, my run record timing is off by a few hours. The run are trigger by a sensor and the sensor ticks timing is correct. So what determines the timing? My Postgres DB? The grpc that runs the run? The dragsters instance? Digit?

Hi, can I ask for clarification on what exactly "run record timing" refers to? What steps are you taking to view the timestamp that doesn't have the expected time?

Also, what version of dagster are you using?

I'm using version is 0.13.17. Run record timing is the Timing column in the latest run table in the sensor and runs view in dagit. If you look at the screenshot you'd think the last run took place ~4hrs ago, but actually it take place a few minute ago, trigger by the recent tick.

Ah, yes…. this is a known issue that is fixed with

0.13.18

. Upgrading will fix the issue going forward, and you can run

dagster instance migrate

to fix the incorrect timestamps for runs. Here are the release notes from that release: https://github.com/dagster-io/dagster/releases/tag/0.13.18

Will upgrade soon. Thanks!

Apologies… you can run

dagster instance reindex

to fix incorrect timestamps for runs. Disclaimer, that command might take a long time.