https://prefect.io logo
Title
y

Yingbo

09/30/2022, 4:28 PM
I'm submitting a flow to Prefect Server for execution using
LocalRun
. I have a single Prefect agent running in a container. I use
IntervalSchedule
and set
interval=timedelta(seconds=60)
. I expected to see my flow run once every minute indefinitely, but instead, I see 10 flows scheduled on the Dashboard. I tried other schedulers -- Cron, etc -- but it always schedules 10 and only 10 runs. Am I missing something or misunderstanding how schedulers work? Thanks
1
1️⃣ 1
b

Bianca Hoch

09/30/2022, 4:35 PM
The UI will only display 10 scheduled runs into the future, but Prefect will continue to schedule the runs (as defined by the scheduler) and display 10 additional runs at a time going forward
Check out our docs here for more information on the scheduler. There's a bullet point which provides some details on the 10 runs you're seeing in the UI.
y

Yingbo

09/30/2022, 4:57 PM
Hi, @Bianca Hoch, thanks for the quick response. I do not see subsequent runs appear in the dashboard. Looking at the docker logs, the Prefect logs stop at the end of the initial 10 runs. The docs you linked states "anytime one is found that hasn't been processed recently, the next 10 runs are scheduled via the creation of
Scheduled
states",
Does this mean that I need to persist some state setting so that it schedules it again even if that flow has been run? I'd like to have it run indefinitely.
b

Bianca Hoch

09/30/2022, 5:13 PM
Hmm..I found an article that may help. A user there mentioned that they had an API error in the towel service logs that affected their schedule.
It might be the case for you? Would you mind sharing the ID for the flow and I can take a look?
y

Yingbo

09/30/2022, 5:18 PM
We are running the flows locally in our own server instance and not in the cloud. Thanks for the link. I haven't heard of this
towel
service but will check with our team to see if it or something like it could be interfering with Prefect.
@Bianca Hoch - thanks for that link. Our tech resolved the issue. It was related to towel. The server is scheduling future runs as expected now.
1
1
🚀 1