Hi everyone, I’m trying to run a scheduled task at 11am UTC 7am EST and this was kinda happened to my flow. Any know any remedy to this. This pipeline is very crucial for my workflow. I’m using the CronClock scheduler btw. Any help is gravely appreciated

Hey @Francis Addae, not fully understanding. Did

SUP pipeline

begin then immediate exit? What does the traceback show?

The traceback showed nothing. Not even a run or an error message. This seems it was about to run then jump to the next day

This is Prefect Core only right? You’re not using a backend like Cloud or Server?

yeah

Ok will ask the team if there are ideas

Yep this looks good. Still waiting on a response from the team. Is your flow simple enough to share?

It’s complicated. Manually running it works fine and the scheduler worked great a day before. It’s just odd that it didn’t work last night

So honestly our recommendation if this is critical is to really run with a backend (Cloud or Server). Cloud has 10000 free task runs every month which is a lot to get started with. We don’t have any concrete ideas how this process ended (and it’s really hard to figure out with limited logs). Do you happen to have a state handler on the Flow? You could also maybe try running with debug level logs so that in the event that this happens again, maybe we could get more info?

I can run it on the cloud but that will cause another problem. Is there a way to get the prefect logs and timestamp when a flow is run through the Cloud or backend server

Yes definitely. The logs are attached to the flow run and the flow records start time and end time

Can save those locally into a variable or into a file

The logs? You can save them into a file by adding a FileHandler to the logger like this. If you use the Local Agent, it will be persisted on your local machine.