19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Hello all! Got an interesting situation happening ...
# ask-communityj
Jose Uribe
04/24/2023, 3:08 PMHello all! Got an interesting situation happening here…recently we did a migration from 0.4.2 to 1.2.1 dagster. For the most part, things went smoothly. However, we are noticing that one of our jobs/schedules seems to be executing twice. Is there any way to track down what’s causing this phantom execution? Would restarting the daemon/dagit help? Any advice is appreciated! From what i can tell though, there’s only one schedule enabled. I do not see any residual schedules in dagit…
Jose Uribe
04/24/2023, 3:11 PMFor context, this 17f8c99e run is the one appearing in the schedule’s history. this 0daa0479 run is seemingly being run by perhaps the “old” schedule? that is my guess as to what might be happening…
c
chris
04/24/2023, 9:40 PMDid I read correctly that you migrated from 0.4.2? Woah! A very early user
chris
04/24/2023, 9:41 PMRegarding your issue, if it’s from that long ago the scheduler implementation completely changed - I wonder if somehow both the old and new scheduler are running? In any case - checking with the team
j
Jose Uribe
04/25/2023, 1:25 PMhaha yep, we’ve been using dagster since about august 2022.
I’m just trying to make sure there’s no remnants of an ‘old’ schedule left anywhere. I double checked some obvious places in the schema and it seems to have properly cleaned up older schedules. If there’s some DB schemas for postgres anywhere (quick search in dagster.io didn’t yield me any schemas/diagrams.) that’d be great!
but for what it’s worth, it seems that today’s scheduled runs properly triggered 1 run of this pipeline. this was after restarting our three services (dagit/daemon/grpc)