17 days ago
hey, so im trying to run now the cron job I have to test it out and the first time I did, it worked fine, but when I am trying to run it again it says cron job successfully invoked but nothing is running
2 Replies
17 days ago
This means it's trying
17 days ago
Wait a few minutes and if it's still stuck abort and try again
It's on and off, I waited a few hours and it started working, now I tried it and it worked first time, then deployed another version and tried to run it, and not running anymore
11 days ago
We have added more CRON workers, so this should be better now.
7 days ago
I'm seeing it be very intermittent as well. I click "Run Now" and it gives the success message but no job is started or recorded in the "Recent Executions", even after page refresh.
Sometimes I need to press the button multiple times before I get a single execution.
We're also seeing no execution being created after clicking "Run now" today. It says "execution started", but nothing appears in the list, even after waiting for 10 minutes or so.
The execution did eventually (15 min or so) appear in our case. If this is expected to take a while, at least sometimes, I would suggest to change the copy of the toast to not say "run immediately".
5 days ago
Same issue. I get the success message then it feels like its nooping. It does seem to run O(minutes) later, but it seems to be very variable. +1 to at a minimum updating the toast copy, and would prefer to have some "is waiting" type state show
5 days ago
We will be looking into this closer this week.
Just another variant of this problem we've seen, in case it's helpful;
sometimes when I click "Run now" it does create an execution in the list immediately, but then clicking the logs shows some logs of the older execution first, and then just "Starting Container", then nothing, for a while.
Screenshot is me having a successful execution, then clicking "Run now" 3 times, resulting in the 3 "Starting container" messages.
In reality, only one container will be running at a time, and I haven't encountered any problems because of this
But the fact that cron doesn't always run is a really big problem