I’m encountering a strange issue with a Scheduler in a Node.js project.
The Situation: I created a Scheduler to trigger a Server Action that handles API requests (SEO ranking checks). After finishing my tests, I deleted the Scheduler via the Wappler UI (Globals > Workflows).
The Problem: Even though the Scheduler no longer exists in the Wappler interface and the corresponding JSON configuration file seems to be gone, the Server Action is still being executed on the previously defined interval. I can see the outgoing API calls and the database updates in my logs.
It seems like the schedule is still "stuck" in the Node.js memory or the internal manager that handles the cron jobs.
What I've tried:
Deleted the Scheduler in Wappler.
Saved all files and deployed.
Checked that the scheduler JSON file is removed from the project folder.
I initially tried increasing the interval from 10 minutes to 10 days, but the Scheduler kept firing every 10 minutes regardless. I then attempted to redeploy the updated schedule multiple times via Wappler, with no success.
Even after manually deleting the scheduler's JSON file directly from the server, the process continued to execute. As a temporary workaround to stop API costs, I have now set all keywords in my database to 'inactive'. It seems the original schedule is stuck in the Node.js memory and completely ignores the fact that the configuration file is gone.
