Add an editable function_args field to the scheduled automation Details panel

Hi Base44 team! Posting this after a productive support thread with one of your reps confirmed it's a real gap worth surfacing here.

The ask

Add an editable function_args (or body) field to the Details tab on scheduled automation panels — so users can self-serve tune limit / mode / threshold values without routing every change through Base44 AI.

Why this matters

Right now, the only way to modify function_args on an existing scheduled automation is through Base44 AI chat. That path has three failure modes I've personally hit in the last week, all related to list_automations truncation at ~10k chars:

1. Wrong-target write. When the target ID isn't in the truncated list, the AI silently picks the closest-named automation and writes to that one instead. Almost mutated my $1-$20 daemon when I asked to update my $20+ hot automation.

2. Update tool can't reach automations not in the truncated list. Even with a verified-correct ID, update_automation returns "automation not found" if the ID didn't appear in the most recent list_automations response. The read tool can find it (different code path), the write tool can't.

3. False confirmation of writes that didn't happen. Earlier this month, AI confirmed it set my limit to 150; AutomationStatus last_summary backed that up; the actual stored value was 75.

A direct UI editor sidesteps all three. Even a read-only display of the current function_args on the Details tab (so users can verify state without a tool call) would be a meaningful first step.

Suggested behavior

• On the Automations panel Details tab, show the current function_args as a structured editor (one row per key, type-aware inputs).

• Save button writes directly to the registration — no AI tool involvement, no list_automations dependency.

• Read-only view by default for production-critical automations; edit unlocked behind a confirm step (the "this will affect the next scheduled run" warning).

Related

While you're in there: the underlying list_automations / update_automation truncation is worth fixing too. If those tools paginated or filtered by ID server-side, the AI failure modes above would mostly disappear even without a UI editor. The two changes are complementary.

Thanks for considering!