From 465a0f9342e28378a541f498439a2f6d4a3f53d3 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 24 Sep 2026 15:02:04 +0000 Subject: [PATCH] docs(changeset): the pending callerParamKeys note no longer lists the schedule trigger as leaving it absent The schedule trigger now states callerParamKeys: [] (landed ae7a35a63b), so the pending note's producer list was false for it. One sentence corrected; nothing else in the note changes. Claude-Session: https://claude.ai/code/session_01Evb5jFDZGKQE9KG4jbMfMF Co-authored-by: Claude --- .changeset/19846-automation-caller-param-keys.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.changeset/19846-automation-caller-param-keys.md b/.changeset/19846-automation-caller-param-keys.md index c5cbff2689..8f13942429 100644 --- a/.changeset/19846-automation-caller-param-keys.md +++ b/.changeset/19846-automation-caller-param-keys.md @@ -12,7 +12,7 @@ A screen whose fields the run's caller already supplied continues without pausin **What the key says.** The keys of the caller's own `params`, recorded before the door seeds anything. An empty array means the caller supplied nothing; an absent key means the producer does not say. -**Who fills it.** The action door (`dispatchFlowAction`: `POST /api/v1/actions/...` and MCP `run_action`) and the trigger door (`buildAutomationContext`: `POST /api/v1/automation/:name/trigger`, the legacy `POST /api/v1/automation/trigger/:name`, and a declarative `type: 'flow'` endpoint). Record-change, schedule, time-relative and webhook triggers, and code calling `execute` directly, leave it absent. `subflow` and `map` nodes drop the parent's list from the child run's context, because it describes the parent's bag. +**Who fills it.** The action door (`dispatchFlowAction`: `POST /api/v1/actions/...` and MCP `run_action`) and the trigger door (`buildAutomationContext`: `POST /api/v1/automation/:name/trigger`, the legacy `POST /api/v1/automation/trigger/:name`, and a declarative `type: 'flow'` endpoint). Record-change, time-relative and webhook triggers, and code calling `execute` directly, leave it absent; the schedule trigger, whose run has no caller, states an empty list (#19900). `subflow` and `map` nodes drop the parent's list from the child run's context, because it describes the parent's bag. **What the screen does with it.** When the key is present, a field is caller-supplied when its name is in the list and `params` holds a value for it; the inference is not consulted. A present value that is not an array names nothing, so the screen pauses. When the key is absent, the inference from #15787 applies unchanged.