Rank 1: Thread
Hi!
Whats the procedure for making a cron function running again thats stuck?
We want to avoid deleting them altogether and re-deploying didn't work.
As per Function overview the next execution is scheduled "25th February"
Votes
0
Replies
19
Participants
Unknown
Messages
20
Rank 1: Thread
Hi!
Whats the procedure for making a cron function running again thats stuck?
We want to avoid deleting them altogether and re-deploying didn't work.
As per Function overview the next execution is scheduled "25th February"
Admin
you can try:
Rank 1: Thread
Aha! Why didn’t I think of that. Seems to have reset the execution timer.
Rank 1: Thread
whats odd is that the function seems to have executed all the time, according to appwrite but nothing ever was really executed
Rank 1: Thread
Rank 1: Thread
(The Usage shows execution, but the web request in the function never sent)
Admin
are you sure it's from the same function?
Rank 1: Thread
Definitely, double checked
Rank 1: Thread
After the cron reset it seems to work just fine now
Admin
did you see stuff in the execution logs of the function?
Rank 1: Thread
Nope it was empty
Admin
how did you check?
Rank 1: Thread
Matching the function id in the URL and the name of the function
Admin
what version of appwrite are you on?
Rank 1: Thread
Not on latest yet, 1.3.1.
However this issue occurred right after the upgrade from 1.2.1
Rank 1: Thread
I cannot reproduce it at all as I am not sure how it happened to begin with, however errors were at zero as well
Admin
so weird...even at 1.2.1 the stat should only be recorded if an execution is created...https://github.com/appwrite/appwrite/blob/0180aff4f540fc4085190d8a0606196dc9db2275/app/workers/functions.php#L367-L378
Rank 1: Thread
I found the underlying display issue
Rank 1: Thread
it seems appwrite displays 30 days by default, however 24h is marked as active
Rank 1: Thread
this should explain it better