Functions > [function name] > Executions -> Create Executions no longer accepts the 'Now' setting

[Social-Betterment]

👟 Reproduction steps

1. Go to 'Functions > [function name] > Executions -> +Create Executions'
2. Click on 'Create'
3. Scroll down to 'Schedule Field'
4. See error: 'This field is required"

👍 Expected behavior

It should execute the function immediately as before. Now you must schedule it at least 1 minute in advance.

👎 Actual Behavior

error: "This field is required" in the Scheduled field.

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

MacOS

🧱 Your Environment

Using the Cloud UI

👀 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?

• I have read the Code of Conduct

[github-actions]

🎯 Agentic Issue Triage

User reports that the "Create Executions" feature in Appwrite Functions no longer accepts the immediate "Now" setting and requires scheduling at least 1 minute in advance. This is a regression in UI functionality that impacts immediate function testing.

(strong)🔍 Analysis & Observations(/strong)

• Issue Type: UI regression/validation bug
• Affected Component: Functions Console - Execution scheduling
• Scope: Cloud instance
• Impact: Medium - workflow disruption, requires workaround
• Severity: This appears to be a recent change/regression as user mentions "no longer accepts"

The issue indicates a validation rule was added or changed that now requires a scheduled time even when immediate execution is desired.

(strong)🐛 Debugging Strategy(/strong)

1. Identify When Regression Occurred:

   • Check recent console/functions commits
   • Review form validation changes
   • Check if this was an intentional change or bug

2. Test Current Behavior:

   • Verify the minimum schedule time requirement (1 minute)
   • Test if leaving the field empty triggers the error
   • Check if there's a "Run Now" alternative button/option

3. Workarounds:

   • Schedule 1 minute in advance as currently required
   • Use CLI to trigger immediate executions: appwrite functions createExecution
   • Use SDK to programmatically trigger functions
   • Use the REST API directly

(strong)💡 Potential Root Causes(/strong)

• Form validation rules changed to require scheduled time
• "Now" option removed but validation not updated
• Timezone handling issue causing immediate execution to fail
• Backend API change requiring scheduled time that wasn't reflected in UI
• Unintended consequence of recent scheduling feature update

(strong)📚 Related Resources(/strong)

• Appwrite Functions - Executions Documentation
• CLI - Functions createExecution
• Functions REST API
• Functions SDK Documentation

(strong)✅ Recommended Next Steps for Team(/strong)

• Verify if "execute now" functionality was intentionally removed
• Check form validation logic for schedule field
• Review recent changes to functions execution UI
• If intentional, add clear "Execute Now" button as alternative
• If bug, restore immediate execution capability
• Update UI/UX to clearly indicate minimum scheduling time if required

AI generated by Agentic Triage

To add this workflow in your repository, run gh aw add githubnext/agentics/workflows/issue-triage.md@0837fb7b24c3b84ee77fb7c8cfa8735c48be347a. See usage guide.

[stnguyen90]

@Social-Betterment thanks for raising this issue! We made changes to the input select component recently.

console/src/lib/components/expirationInput.svelte

Lines 140 to 147 in a8bdb86

	<InputSelect
	required
	{helper}
	{options}
	id="preset"
	label={selectorLabel}
	bind:value={expirationSelect}
	on:change={() => (hasUserInteracted = true)} />

This may have lead to things breaking. I've reported it to the team.

Related: