cloudflare / cloudflare/developer-platform

dashboard: Worker Cron Job Scheduler Fails to Save

Open
#30 1 comment 0 reactions 0 assignees View on GitHub
awaiting-response:cloudflare
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### What versions & operating system are you using?

Safari 26.5 and Chrome 148.0.7778.179

### Please provide a link to a minimal reproduction

https://plain-fire-41bd.bach-project-services.workers.dev

### Describe the Bug

When I am using the web to attempt to add a cronjob trigger, it fails to save. To reproduce the issue, I go to settings -> Add next to Trigger Events -> Cron triggers -> Add (the default doesn't work). When clicking the final Add button, nothing happens to the interface.

I also attempted to change the frequency to every 1 minute, every 1 hour, every 3 hours, and every 5 hours, none of which would save.

When I go to my browser console, I can see that there were 2 400 responses returned after clicking the save button. I then went to the network tab and see that the browser is sending a blank string as the cron schedule which fails on the validate and describe endpoints and therefore does not actually save.

Workaround: In the sidebar panel where you choose your frequency, choose the tab for "Cron expression". Here, you can write your own cron schedule the way you would with a cron job on any other server/computer.

The issue: the web interface is not interpreting the dropdown and text field inputs correctly and therefore sending a blank string to be validated which fails. Another related issue is that when this fails, there should be some form of an error message that appears to the user allowing them to make changes but this does not happen either, leaving the user confused on what happened.

### Please provide any relevant error logs

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.