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"
you can try:
- remove cron schedule (make sure to click Update)
- add the cron schedule back
Aha! Why didn’t I think of that. Seems to have reset the execution timer.
whats odd is that the function seems to have executed all the time, according to appwrite but nothing ever was really executed
(The Usage shows execution, but the web request in the function never sent)
are you sure it's from the same function?
Definitely, double checked
After the cron reset it seems to work just fine now
did you see stuff in the execution logs of the function?
Nope it was empty
how did you check?
Matching the function id in the URL and the name of the function
what version of appwrite are you on?
Not on latest yet, 1.3.1. However this issue occurred right after the upgrade from 1.2.1
I cannot reproduce it at all as I am not sure how it happened to begin with, however errors were at zero as well
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
I found the underlying display issue
it seems appwrite displays 30 days by default, however 24h is marked as active
this should explain it better
Recommended threads
- Unable to create records with other user...
are we able to create records in collections with permissions of different user than the caller of this request? (with document security on) I have backend func...
- Sometimes this function shows an error l...
1. Synchronous function execution timed out. Use asynchronous execution instead, or ensure the execution duration doesn't exceed 30 seconds.\nError Code: 408 2...
- Custom Topic sent from Function (with sc...
Can I send a message on a custom topic? So clients can subscribe to them?