Hello!
I have an issue when I schedule a function with minutes other than 0 or *, for example 30 1 * * *.
I deploy my function with the CLI and the schedule parameter on the json but the schedule is not active on my function. If I update my cron value on the console I have an error « Please enter a valid cron expression ».
What can I do to activate my schedule on my function?
I also add an issue on the Appwrite GitHub with screenshots : https://github.com/appwrite/appwrite/issues/5719
Thanks for your help! 🙏
it definitely seems like something might be wrong with the cron validation...I'll raise that with the team.
As for the problem about the function executing....how do you know the schedule isn't active?
Ok, thank you 😊 The schedule isn’t active because there isn’t clock icon next to the function ID on the functions list. I have an other function with * * * * * cron value and there is a clock icon and the schedule works correctly.
Honestly, I'm not so sure about the clock icon.
You said it's not executing...are you considering the timezone you're setting? It should be UTC
Ok, I just redeployed the function, I will see tomorrow if the function was executed (I am in France). I come back to you quickly.
It's ok, my schedule was launch this night 👍 It's just a problem on the first function deploy, when you change the cron value with * * * * * for example and you redeploy the function it works. Thank you for your help.
Recommended threads
- ClientException with SocketException: Cl...
hi <@564158268319203348> i have noticed this 500 status code in my function requests, it seems its not able to connect to the internet in the function as reque...
- NEW ERROR Invalid document structure: At...
Error: ```AppwriteException: document_invalid_structure, Invalid document structure: Attribute "pb.kmsgxPkgInfo.id_info" must be an array (400)``` I’m encounter...
- Issues with executor in Appwrite 1.9.0
Hi, I’ve recently did a fresh install of appwrite 1.9.0 self hosted and when I run a function, it just waits indefinite This is the error from the log: [Er...