How I Fixed Backendless Timer Logic Not Triggering in JavaScript Cloud Code

Hello

I recently deployed a Backendless Cloud Code timer in JavaScript that was supposed to run every hour & update a few user records. :innocent: The timer appeared in the console & was enabled but it never actually executed. :slightly_smiling_face:

No logs, no updates just silence. I confirmed the function was deployed properly and the logic was correct. :upside_down_face:

After troubleshooting; I realized that I hadnโ€™t explicitly specified the startDate& frequency properties correctly in the timer.json configuration file. Backendless requires these to be clearly defined, even if youโ€™re deploying via the CLI. :thinking:

Once I updated the config and redeployed; the timer fired as expected. This Backendless Timer Configuration Guide was crucial in resolving the issue. :thinking:

During the process, a teammate whoโ€™s newer to programming asked me what is java, since they noticed Backendless also supports Java-based Cloud Code. :innocent:

It was a good opportunity to explain the difference between Java and JavaScript, especially when working across both environments in the same backend platform.

Thank you !! :slightly_smiling_face:

Hello Nikave Amirei!

Welcome to the community! :waving_hand:
Thanks for sharing your experience โ€” that kind of insight is super helpful for others who might run into the same issue.
Glad you got it working, and great job spotting the config detail in timer.json โ€” those little things can be tricky!

Also, love that you took the time to help your teammate understand the Java vs JavaScript distinction :raising_hands:

Regards,
Alexander