8000 🐛 Bug Report: Incorrect input type for cron schedule in a function · Issue #9880 · appwrite/appwrite · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

🐛 Bug Report: Incorrect input type for cron schedule in a function #9880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
davidmartin opened this issue May 23, 2025 · 0 comments · Fixed by appwrite/console#1880
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@davidmartin
Copy link

👟 Reproduction steps

Description:

The input field for setting the function schedule is of type email, which prevents entering a valid cron expression.

Error Message:

Please include an '@' in the email address. '30 7 * * ' is missing an '@'.

Steps to Reproduce:

  1. Go to a function.
  2. Navigate to the Settings tab.
  3. Try to add a cron expression in the Schedule field (e.g., 30 7 * *).
  4. An input validation error appears.

Temporary Workaround:

Manually change the input type from email to text using the browser dev tools. 😅

Image

👍 Expected behavior

The field should accept valid cron expressions without requiring an '@' symbol.

👎 Actual Behavior

An error is triggered because the input is incorrectly expecting an email format.

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

Version Appwrite selfhosted: 1.7.2

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants
0