rubenf
rubenf•4mo ago

No concurrency limits is the right way

No concurrency limits is the right way to do it. WDYM by none of them will actually execute ?
17 Replies
Kaspar
Kaspar•4mo ago
I created this scenario and it worked perfectly as expected, until...
No description
No description
No description
Kaspar
Kaspar•4mo ago
... I also configured a retry handler for the schedule which gets it stuck in some loop and none of the schedules execute anymore. 😛
No description
No description
No description
Kaspar
Kaspar•4mo ago
I cancelled the run and it looks like this:
No description
Kaspar
Kaspar•4mo ago
Do also note that it ran for 5 minutes but the script had a timeout of 1 minute
rubenf
rubenf•4mo ago
will investigate, thanks for feedback @Kaspar I can't reproduce also it didn't ran for 5 minutes, the flow with the retry ran for 5 minutes but spent all of its time rescheduling the inner job with the key Ah I think I know the issue should be fixed in very latest
Kaspar
Kaspar•4mo ago
"also it didn't ran for 5 minutes, the flow with the retry ran for 5 minutes but spent all of its time rescheduling the inner job with the key" yep-yep, phrased it a bit bad Let me know when I can run the test again on app.windmill.dev gm @rubenf I ran the test again and it worked as expected. Thanks for the swift update, again!
Kaspar
Kaspar•4mo ago
I have a question or feedback about understanding the execution time though. As I understood, the re-scheduling doesn't count as "execution second" when it comes to the billing, but from looking at the charts and Runs then they do show "300 seconds" type of numbers, even though the script ran 20 seconds and rest of it was re-scheduling. From my understanding, the billing in this case is for the 20 seconds and not the 280 seconds of re-scheduling, right?
No description
rubenf
rubenf•4mo ago
correct the billing is only for the jobs executed
Kaspar
Kaspar•4mo ago
Cool, but do you agree it's hard for me to tell that?
rubenf
rubenf•4mo ago
Yes but I do think the numbers shown are the right ones in every context for schedules you want to know e2e how long it took
Kaspar
Kaspar•4mo ago
Right, I see the 5.1 sec on the bottom-right
No description
Kaspar
Kaspar•4mo ago
But from the general Runs tab the re-scheduled ones still look like outliers of execution time:
No description
Kaspar
Kaspar•4mo ago
At a glance*
rubenf
rubenf•4mo ago
yes that one is not intuitive and wrong I'll see what I can do
Kaspar
Kaspar•4mo ago
tiny ping
rubenf
rubenf•4mo ago
yup it's on our radar