Schedule daily recurring workflow with Bubble personal plan | Bubble.io Tutorials | Planetnocode.com 

Glad it was helpful!

Thank you Alexander!

how?

Your Bubble app needs 1 cron-job for every version of your app. For most people that's 2 cron-jobs: (1) Dev, (2) Live. Your live version endpoint will be the same URL just remove "/version-test/".

Do you have the API Workflow set to run without authentication?

Heya, I've seen you've been trying to debug the cron-job recurring workflow workaround on our website too. I've just reached out using the email attached to the comments, please check your inbox.

Have you recently deployed your dev version to live? Has your live version definitely got the same workflow set up?

@@planetnocode well, I keep deploying the app every time I make changes - how does it affect the cron-job? And yes: I have setup 1 workflow which exists in both the test and live version of my app -> they share the same url path to receive the cron-job post, but I’ve setup 2 different cron-jobs: 1 for the test-version (includes the “version-test” parameter in the url) and 1 for the live-version (without the “version-test” parameter). I suppose that’s correct?! Those are also the correct root urls as shown in my bubble api settings

@@planetnocode well, I keep deploying the app every time I make changes - how does it affect the cron-job? And yes: I have setup 1 workflow which exists in both the test and live version of my app -> they share the same url path to receive the cron-job post, but I’ve setup 2 different cron-jobs: 1 for the test-version (includes the “version-test” parameter in the url) and 1 for the live-version (without the “version-test” parameter). I suppose that’s correct?! Those are also the correct root urls as shown in my bubble api settings

A 404 error suggesting that the endpoint can’t be found. Have you removed initialize from the endpoint? If you’re referring to your live app, have you deployed to live since setting up the cron job endpoint in your dev version?

The call needs to be POST. Are you getting an authentication error?

Thanks for all the detail. Have you removed 'initialize' from the end of the API endpoint after you've tested it in Cron Job?

@@planetnocode Hi, thanks for replying. Yes and just then i start getting the 401's. EDIT: The App is set to private.

When you say 'set to private' are you referring to 'Protect your app in run-mode' begin checked in your Settings? Do you require a username and password to be entered into a browser dialogue popup when you first access the app?

@@planetnocode Aah, i deleted my own post. Tried to post a Loom video. The settings you mention are disabled. I was refering to the settings one row above. I only need to enter a password to access bubble.io itself. Not the app pages. Any idea whats missing? Thanks!

Thanks for the quick response. This doesn't seem to be an easy thing to explain and understand in the RU-vid comments. May I recommend booking a free 15 min Bubble coaching session with one of our team? Full details: www.planetnocode.com/coaching

Couple of thoughts: Have you recently deployed to your live version, does your live version definitely have this endpoint? Have you removed /version-test/ and ‘initialize’ from the endpoint url if you wish to trigger a workflow on your live version?

Thank you for your quick reply... I am currently testing in Development mode. I tried testing it in live mode after removing 'versions-test' and 'initialize' but its still showing 401 unauthorized error

401 errors are issues with authorization. Is your app password protected in the Settings > General tab? Have you tried using the app API key to authorize or trying Run without authorization just to test it?

No you'll need a different cron job for your dev and live version. Just change 'version-test' to 'version-live' for your endpoint URL. However, it is worth noting that Bubble's new plans include an improved recurring workflow action that is no longer limited to monthly on the Personal plan. This video's workaround may not be needed anymore.

Thank you@@planetnocode for the reminder. Does this "note" still hold when you want to cause the trigger after every hour or say after some minutes? The execution goes fine on the cron-jobs side, but the trigger doesn't happen on the bubble's side. Could I have gone wrong somewhere?

Recurring Workflows look to now be available on every paid plan with the minimum interval of each day. manual.bubble.io/help-guides/logic/workflows/events/backend-events#recurring-events

Thank you. This will help.

@@planetnocode Hey there, I am on the personal plan currently and every-time I go to set a reoccuring workflow it says that my plan only allows me to set 1 recurring workflow per thing. I already have 4 recurring workflows that give my users more uses of parts of my app according to their paid plan, but now I am trying to set it up so that when they press a button, it posts a tweet to twitter every single day. I have everything setup but for some reason when I go to set the recurring plan, nothing ever happens, which is why I was going to try cronjobs but that didn't work either. Any ideas?

You can achieve this with a custom cron-job expression. Here's some examples stackoverflow.com/questions/16717930/how-to-run-crontab-job-every-week-on-sunday

@@planetnocode ahhhhh i see! wonderful My friend. Wonderful!

Are you on a paid Bubble plan? API workflows and API Endpoints are not available on the free tier.

Thank you.

Is your app running with a paid Bubble account?

@@planetnocode Yes, it's finally working, just checked this workflow can be run without authentication

@@planetnocode Thanks for the lesson man, appreciate this!

This is no longer a limitation. When Bubble updated their pricing in 2023 they made daily recurring workflows available across all paid plans. More details here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5kbPAKAIInw.html

@@planetnocode I realised that, but I needed hourly workflows, so I still ended up using the above mentioned method.