Diagnostics β
Every error and warning Mermaid Flow can show for a workflow. An error means the workflow can't run as written. A warning points at something that runs but is likely a mistake.
| Id | Severity | Applies to | In one line |
|---|---|---|---|
| Placing nodes | |||
TASK_OUTSIDE_FLOW | error | task, decision | A task or decision sits outside every flow. |
CONNECTOR_NOT_ROOT | error | connector | A connector sits inside a flow. |
INPUT_NOT_ROOT | error | input | An input sits inside a flow. |
FLOW_EMPTY | warning | flow | A flow is empty, or holds only other flows. |
ID_DUPLICATE | error | any node | Two nodes share an id. |
SHAPE_UNSUPPORTED | error | any node | A node uses a shape that isn't available. |
| Writing tasks | |||
INSTRUCTION_MISSING | error | task | A task has no instruction. |
TASK_MISSING_LABEL | error | task | A task has an empty label and no instruction. |
INSTRUCTION_PLACEHOLDER | error | flow, task, decision, arrow | An instruction still holds a placeholder such as <REPO>. |
| Referring to things | |||
REF_UNRESOLVED | error | arrow, dotted link | A link points at an id no node has. |
REF_OUT_OF_SCOPE | error | arrow | An arrow reaches into a flow from outside (inputs excepted). |
REF_FORWARD | β | β | No longer raised. |
| Connectors | |||
CONNECTOR_UNBOUND | error | connector | The connector has no link, except to other connectors. |
CONNECTOR_ID_RESERVED | error | connector | A connector uses the reserved id system. |
CONNECTOR_BINDING_DUPLICATE | warning | dotted link | The same task and connector are linked twice. |
| Arrows | |||
EDGE_KIND_INVALID | error | arrow, dotted link | A link joins two shapes it can't join. |
EDGE_LABEL_UNSUPPORTED | error | arrow | An arrow that isn't a branch has a label. |
EDGE_INSTRUCTION_UNSUPPORTED | error | arrow | An arrow that isn't a branch has an instruction. |
EDGE_REDUNDANT | warning | arrow | The same arrow is drawn twice. |
EDGE_SHORTCUT | error | arrow | An arrow skips a step its source already reaches. |
EDGE_UNSUPPORTED | error | any link | A link uses an operator that isn't available. |
PIPE_PREFER_CHAINED | β | β | No longer raised. |
| Decisions | |||
DECISION_TOO_FEW_BRANCHES | warning | decision | A decision has fewer than two branches. |
DECISION_BRANCH_UNGUARDED | error | branch | A branch has no label. |
DECISION_BRANCH_AMBIGUOUS | warning | branch | Two branches share a label. |
DECISION_BRANCH_SHARED_TARGET | error | branch | Two branches go to the same node. |
| How the workflow moves | |||
FLOW_CONFLICTING_TRANSITIONS | error | last step of a flow, arrow | A flow and its last step both say what comes next. |
CYCLE_NO_EXIT | error | loop | A loop, or a loop inside it, takes no decision branch out. |
CYCLE_TASK_EXIT | warning | arrow | A task's arrow leaves a loop, so its target runs every lap. |
UNREACHABLE_COMPONENT | warning | any node | Nothing leads to a node. |
| Settings | |||
METADATA_UNKNOWN_KEY | warning | any node, branch | A setting the shape doesn't take. |
METADATA_INVALID_VALUE | error | any node | A setting has a value it can't take. |
METADATA_REQUIRED | error | input, connector | A required setting is missing. |
METADATA_KEY_CONFLICT | error | input | Two settings that exclude each other are both set. |
Placing nodes β
TASK_OUTSIDE_FLOW β
error Β· task, decision Β· active
Why. A task or decision is a step of a flow, so it has to sit inside one.
Code:
agentflow TB
summarise["Summarise"]@{ instruction: "Summarise the ticket in two lines." }
Task "summarise" is outside every flow. Move it into a flow.
Fix. Wrap the task or decision in flow id β¦ end.
Related. CONNECTOR_NOT_ROOT, INPUT_NOT_ROOT
CONNECTOR_NOT_ROOT β
error Β· connector Β· active
Why. A connector is shared by the whole workflow, so it can't belong to one flow.
Code:
agentflow TB
flow triage["Issue triage"]
connector github["GitHub"]@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read -.- github
end
Connector "github" is inside flow "triage", but connectors belong at the top level of the workflow. Move it out of the flow.
Fix. Move the connector line above or below the flow, outside every flow β¦ end. Its dotted links can stay where they are.
Related. TASK_OUTSIDE_FLOW, INPUT_NOT_ROOT
INPUT_NOT_ROOT β
error Β· input Β· active
Why. An input starts flows from outside, so it can't sit inside one.
Code:
agentflow TB
flow triage["Issue triage"]
weekday[/"Weekdays at 09:00"/]@{ trigger: "schedule", cron: "0 9 * * 1-5" }
read["Read issues"]@{ instruction: "Summarise every open issue." }
end
Input "weekday" is inside flow "triage", but inputs belong at the top level of the workflow. Move it out of the flow.
Fix. Move the input outside every flow, and point an arrow from it to the flow: weekday --> triage.
Related. CONNECTOR_NOT_ROOT, EDGE_KIND_INVALID
FLOW_EMPTY β
warning Β· flow Β· active
Why. A flow that holds nothing, or only other flows, has nothing of its own to run. Any other shape directly inside it counts as something to run.
Code:
agentflow TB
flow drafts["Drafts"]
end
Flow "drafts" is empty. Add a task to it, or remove it.
A flow that only holds other flows is flagged too:
Code:
agentflow TB
flow support["Support"]
flow triage["Triage"]
read["Read ticket"]@{ instruction: "Read the ticket." }
end
end
Flow "support" only holds other flows, so it has nothing of its own to run. Add a task to it.
Fix.
- Add a task to the flow.
- Remove the flow.
Related. TASK_OUTSIDE_FLOW
ID_DUPLICATE β
error Β· any node Β· active
Why. Arrows and settings find a node by its id. Two nodes with one id make every reference to it unclear.
Code:
agentflow TB
flow blog["Blog post"]
draft["Draft"]@{ instruction: "Write a 600-word post." }
draft["Edit"]@{ instruction: "Tighten the post to 400 words." }
end
"draft" is the id of 2 nodes. Give each node its own id.
Fix. Rename one of the nodes, and update the arrows that should point at it.
A line such as draft@{ instruction: "β¦" } only adds settings to a node, so it never counts as a second node.
Related. REF_UNRESOLVED
SHAPE_UNSUPPORTED β
error Β· any node Β· active
Why. The node's shape is one Mermaid draws, but the workflow can't run it. While a diagram has an unavailable shape or link, the other checks are skipped, so fix this first.
The message names the node and its shape:
Node "<id>" uses the "<shape>" shape, which isn't available. Use "task", "flow" or "decision".Fix. Rewrite the node as one of the available shapes: a task, decision, input, connector or flow.
Related. EDGE_UNSUPPORTED
Writing tasks β
INSTRUCTION_MISSING β
error Β· task Β· active
Why. A label names a step, but it doesn't say what the step should do. A task without an instruction can't run.
Code:
agentflow TB
flow support["Support"]
summarise["Summarise"]
end
Task "summarise" has no instruction, so the workflow can't run it. Add an instruction that says what the step should do.
Fix. Add an instruction: summarise["Summarise"]@{ instruction: "Summarise the ticket in two lines." }. An instruction of only spaces counts as missing.
Related. TASK_MISSING_LABEL, INSTRUCTION_PLACEHOLDER
TASK_MISSING_LABEL β
error Β· task Β· active
Why. A task whose label is empty, and that has no instruction, has nothing to do.
Code:
agentflow TB
flow support["Support"]
summarise[" "]
end
Task "summarise" has no label or instruction, so it has nothing to do. Add an instruction.
Fix. Add an instruction, and a label if you want one.
Related. INSTRUCTION_MISSING
INSTRUCTION_PLACEHOLDER β
error Β· flow, task, decision, arrow Β· active
Why. A value in capitals inside angle brackets, such as <REPO>, is a placeholder nobody filled in. The step has no real instruction to run.
Code:
agentflow TB
flow triage["Issue triage"]
open["Open issue"]@{ instruction: "Open an issue in <REPO> describing the bug." }
end
The instruction on task "open" still has the placeholder "<REPO>". Replace it with a real value.
Fix. Replace each placeholder with the real value. Lowercase tokens such as <repo> are not placeholders and are left alone.
Related. INSTRUCTION_MISSING
Referring to things β
REF_UNRESOLVED β
error Β· arrow, dotted link Β· active
Why. A link points at an id that no node has, usually a typo. The workflow can't follow it.
Code:
agentflow TB
flow blog["Blog post"]
draft["Draft"]@{ instruction: "Write a 600-word post." }
edit["Edit"]@{ instruction: "Tighten the post to 400 words." }
draft --> eddit
end
An arrow connects to "eddit", but there's no node with that id. Check the spelling, or add the node.
Fix.
- Fix the spelling of the id.
- Add the missing node.
Related. ID_DUPLICATE, REF_OUT_OF_SCOPE
REF_OUT_OF_SCOPE β
error Β· arrow Β· active
Why. The nodes inside a flow belong to that flow. An arrow from outside the flow can reach the flow, but not the nodes inside it.
Code:
agentflow TB
flow team["Team"]
plan["Plan"]@{ instruction: "Split the work into two parts." }
flow writers["Writers"]
write["Write"]@{ instruction: "Write the first part." }
end
plan --> write
end
"plan" can't connect to "write", because "write" is inside flow "writers". Point the arrow at flow "writers" instead.
Fix. Point the arrow at the flow the message names. An input's arrow is never flagged: an input can start any flow, even one inside another flow.
Related. REF_UNRESOLVED
REF_FORWARD β
β Β· deprecated
No longer raised. You can use an id in an arrow before the line that defines the node.
Connectors β
CONNECTOR_UNBOUND β
error Β· connector Β· active
Why. A connector is only used through the tasks linked to it. With no link, nothing can use it. Any link counts here except one to another connector: a link from anything but a task is EDGE_KIND_INVALID instead.
Code:
agentflow TB
connector github["GitHub"]@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
end
Connector "github" isn't linked to any task, so nothing can use it. Link it to the task that needs it: <task> -.- github.
Fix.
- Link the connector to the task that needs it:
read -.- github. - Remove the connector.
Related. EDGE_KIND_INVALID, CONNECTOR_BINDING_DUPLICATE
CONNECTOR_ID_RESERVED β
error Β· connector Β· active
Why. The id system belongs to the built-in tools. A connector with that id would clash with them.
Code:
agentflow TB
connector system["Tools"]@{ protocol: "mcp", url: "https://example.com/mcp" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read -.- system
end
The id "system" is reserved for built-in tools. Give this connector a different id.
Fix. Rename the connector, and update its dotted links. A task or flow can still use the id system.
Related. ID_DUPLICATE
CONNECTOR_BINDING_DUPLICATE β
warning Β· dotted link Β· active
Why. A dotted link has no direction, so read -.- github and github -.- read are the same link. The second one adds nothing.
Code:
agentflow TB
connector github["GitHub"]@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read -.- github
github -.- read
end
"read" is already linked to connector "github". Remove the extra dotted link.
Fix. Remove the extra dotted link. Different tasks can each link to the same connector.
Related. EDGE_REDUNDANT, CONNECTOR_UNBOUND
Arrows β
EDGE_KIND_INVALID β
error Β· arrow, dotted link Β· active
Why. Each link joins only certain shapes. An arrow joins flows, tasks and decisions, or an input to a flow. A dotted link joins a task and a connector. The message says which end is wrong.
Code:
agentflow TB
connector github["GitHub"]@{ protocol: "mcp", url: "https://api.githubcopilot.com/mcp/" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read --> github
end
Connector "github" can't be the target of an arrow. Link it with a dotted link instead: <task> -.- github.
Fix.
- Link a connector to a task with a dotted link:
read -.- github. - Link a connector to a task, not to a flow or a decision.
- Point an input's arrow at a flow, and don't point arrows into an input.
Related. CONNECTOR_UNBOUND, EDGE_UNSUPPORTED
EDGE_LABEL_UNSUPPORTED β
error Β· arrow Β· active
Why. A label tells a decision which branch is which. On any other arrow, nothing reads it.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Summarise the ticket in two lines." }
reply["Reply"]@{ instruction: "Write a polite reply that answers the ticket." }
read -- then --> reply
end
The arrow from "read" to "reply" has a label, but only branches leaving a decision can have one. Remove the label, or add a decision.
Fix.
- Remove the label:
read --> reply. - Add a decision before the arrow, and make it a branch.
Related. EDGE_INSTRUCTION_UNSUPPORTED, DECISION_BRANCH_UNGUARDED
EDGE_INSTRUCTION_UNSUPPORTED β
error Β· arrow Β· active
Why. An instruction on an arrow only has a place on a branch. On any other arrow, it isn't clear which step should follow it.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Summarise the ticket in two lines." }
reply["Reply"]@{ instruction: "Write a polite reply that answers the ticket." }
read e1@--> reply
e1@{ instruction: "Keep the customer's name." }
end
The arrow from "read" to "reply" has an instruction, but only branches leaving a decision can have one. Move it into a task.
Fix. Move the guidance into the instruction of the next task, or add a task for it.
Related. EDGE_LABEL_UNSUPPORTED
EDGE_REDUNDANT β
warning Β· arrow Β· active
Why. Drawing the same arrow twice adds nothing. It is usually left over from an edit.
Code:
agentflow TB
flow blog["Blog post"]
draft["Draft"]@{ instruction: "Write a 600-word post." }
edit["Edit"]@{ instruction: "Tighten the post to 400 words." }
draft --> edit
draft --> edit
end
There is already an arrow from "draft" to "edit". Remove the extra one.
Fix. Remove the extra arrow. a --> b and b --> a are a loop, not a repeat.
Related. DECISION_BRANCH_SHARED_TARGET, CONNECTOR_BINDING_DUPLICATE
EDGE_SHORTCUT β
error Β· arrow Β· active
Why. A task continues along every arrow that leaves it. If it already reaches a step through another node, a direct arrow to that step hands it the same work a second time.
Code:
agentflow TB
flow blog["Blog post"]
draft["Draft"]@{ instruction: "Write a 600-word post." }
edit["Edit"]@{ instruction: "Tighten the post to 400 words." }
publish["Publish"]@{ instruction: "Publish the edited post." }
draft --> edit --> publish
draft --> publish
end
The arrow from "draft" to "publish" skips a step: "draft" already reaches "publish" through "edit". Remove this arrow.
Fix. Remove the arrow that skips the step. Branches leaving a decision are never shortcuts.
Related. EDGE_REDUNDANT
EDGE_UNSUPPORTED β
error Β· any link Β· active
Why. The link uses an operator Mermaid draws, but the workflow can't follow it. While a diagram has an unavailable shape or link, the other checks are skipped, so fix this first.
The message names the link by its two ends:
The arrow from "<a>" to "<b>" uses "<operator>", which isn't available. Use an arrow (-->) to connect steps, or a dotted link (-.-) to link a connector.Fix. Use an arrow (-->) between steps, or a dotted link (-.-) between a task and a connector.
Related. SHAPE_UNSUPPORTED, EDGE_KIND_INVALID
PIPE_PREFER_CHAINED β
β Β· deprecated
No longer raised. A chain such as a --> b --> c and one arrow per line mean the same.
Decisions β
DECISION_TOO_FEW_BRANCHES β
warning Β· decision Β· active
Why. A decision picks between branches. With fewer than two, there is nothing to choose.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Read the ticket." }
kind{"Bug?"}
fix["File a bug"]@{ instruction: "Open a bug report with steps to reproduce." }
read --> kind
kind -- yes --> fix
end
Decision "kind" has only 1 branch. Add another, because a decision needs at least 2.
A decision with no branches at all reads:
Decision "<id>" has no branches. Add at least 2.Fix.
- Add another labelled branch.
- Replace the decision with a regular arrow (
-->).
Related. DECISION_BRANCH_UNGUARDED
DECISION_BRANCH_UNGUARDED β
error Β· branch Β· active
Why. A decision chooses a branch by its label. A branch with no label can't be chosen. An instruction on the branch doesn't replace the label.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Read the ticket." }
kind{"Bug?"}
fix["File a bug"]@{ instruction: "Open a bug report with steps to reproduce." }
answer["Answer"]@{ instruction: "Reply using the help center." }
read --> kind
kind -- yes --> fix
kind --> answer
end
The branch from "kind" to "answer" has no label, so the decision can't choose it. Add a label.
Fix. Add a label: kind -- no --> answer.
Related. DECISION_BRANCH_AMBIGUOUS, EDGE_LABEL_UNSUPPORTED
DECISION_BRANCH_AMBIGUOUS β
warning Β· branch Β· active
Why. Two branches with the same label can't be told apart. Each one is flagged.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Read the ticket." }
kind{"Bug?"}
fix["File a bug"]@{ instruction: "Open a bug report with steps to reproduce." }
answer["Answer"]@{ instruction: "Reply using the help center." }
read --> kind
kind -- yes --> fix
kind -- yes --> answer
end
Decision "kind" has more than one branch labelled "yes". Give each branch its own label.
Fix. Give each branch its own label.
Related. DECISION_BRANCH_SHARED_TARGET
DECISION_BRANCH_SHARED_TARGET β
error Β· branch Β· active
Why. Two branches that go to the same node lead to the same place, so the choice changes nothing. Each one is flagged.
Code:
agentflow TB
flow support["Support"]
read["Read ticket"]@{ instruction: "Read the ticket." }
kind{"Bug?"}
fix["File a bug"]@{ instruction: "Open a bug report with steps to reproduce." }
read --> kind
kind -- yes --> fix
kind -- maybe --> fix
end
Decision "kind" has more than one branch to "fix". Combine them into one branch.
Fix.
- Point one of them at a different node.
- Combine the branches into one. If that leaves the decision with one branch, it is
DECISION_TOO_FEW_BRANCHES: replace the decision with a regular arrow (-->).
Related. DECISION_BRANCH_AMBIGUOUS, EDGE_REDUNDANT
How the workflow moves β
FLOW_CONFLICTING_TRANSITIONS β
error Β· last step of a flow, arrow Β· active
Why. When a flow finishes, either the flow says what comes next or its last step does. If both do, it isn't clear which arrow applies.
Code:
agentflow TB
flow research["Research"]
find["Find sources"]@{ instruction: "Find three recent sources on the topic." }
end
flow write["Write"]
draft["Draft"]@{ instruction: "Write a 600-word post from the sources." }
end
flow archive["Archive"]
save["Save sources"]@{ instruction: "Save the source links to the archive." }
end
research --> write
find --> archive
Flow "research" continues to "write" when it finishes, but its last task "find" also has an arrow to "archive". Keep one of the two.
Fix.
- Remove the flow's arrow and keep the step's.
- Remove the step's arrow and keep the flow's.
Related. REF_OUT_OF_SCOPE
CYCLE_NO_EXIT β
error Β· loop Β· active
Why. A loop ends only when a decision in it takes a branch that leads out. Without one, the loop runs forever. An arrow out of a task is not a way out, because a task continues along every arrow that leaves it. Neither is the arrow out of a flow whose last step is a decision: it is taken whatever the decision picks.
Code:
agentflow TB
flow editor["Editor"]
draft["Draft"]@{ instruction: "Write a 300-word product description." }
review["Review"]@{ instruction: "List what to improve in the draft." }
draft --> review
review --> draft
end
The loop through "draft" never ends, because it has no decision with a branch leading out. Add a decision with a branch that leaves the loop.
When the loop has a decision but none of its branches leads out, the message reads:
The loop through "<id>" never ends, because no decision in it has a branch leading out. Add a branch that leaves the loop.A loop that can end can still hold a smaller loop that can't. Here check can leave the big loop, but draft and research go round each other without taking any of check's branches.
Code:
agentflow TB
flow editor["Editor"]
draft["Draft"]@{ instruction: "Write a 300-word product description." }
check{"Good enough?"}
publish["Publish"]@{ instruction: "Publish the approved description." }
research["Research"]@{ instruction: "Find one more fact for the draft." }
draft --> check
check -- no --> draft
check -- yes --> publish
draft --> research
research --> draft
end
The loop through "draft" never ends, because it has no decision with a branch leading out. Add a decision with a branch that leaves the loop.
Fix. Make every loop take a decision branch, with one branch that goes back and one that leaves:
draft --> check
check -- no --> draft
check -- yes --> publishRelated. CYCLE_TASK_EXIT, DECISION_TOO_FEW_BRANCHES
CYCLE_TASK_EXIT β
warning Β· arrow Β· active
Why. A task continues along every arrow that leaves it. When a task in a loop also points outside the loop, the target runs on every lap, not once at the end.
Code:
agentflow TB
flow editor["Editor"]
draft["Draft"]@{ instruction: "Write a 300-word product description." }
check{"Good enough?"}
publish["Publish"]@{ instruction: "Publish the approved description." }
notify["Notify"]@{ instruction: "Tell the team a new draft is ready." }
draft --> check
check -- no --> draft
check -- yes --> publish
draft --> notify
end
Task "draft" has an arrow leaving its loop to "notify", so "notify" runs on every lap. To run it once after the loop, start that arrow from the loop's decision.
Fix.
- Start the arrow from the loop's decision, as a labelled branch.
- Keep it, if the target should run on every lap.
Related. CYCLE_NO_EXIT
UNREACHABLE_COMPONENT β
warning Β· any node Β· active
Why. A node that nothing leads to never runs. You won't see this warning on a diagram. Every step with no arrow into it counts as a starting point. So does the first step written in a loop that nothing leads into. The id stays in the list so that tools reading diagnostics know it.
The message has one of these forms, for a node in a flow or at the top level of the workflow:
Nothing in flow "<flow>" leads to "<id>", so it never runs. Add an arrow to it, or remove it.Nothing in the workflow leads to "<id>", so it never runs. Add an arrow to it, or remove it.Fix. Add an arrow to the node, or remove it.
Related. FLOW_EMPTY
Settings β
METADATA_UNKNOWN_KEY β
warning Β· any node, branch Β· active
Why. The shape doesn't take this setting, so it is ignored. It is usually a typo.
Code:
agentflow TB
flow support["Support"]
summarise["Summarise"]@{ instruction: "Summarise the ticket in two lines.", promt: "Be brief." }
end
Task "summarise" has an unknown setting "promt". Check the spelling, or remove it.
Fix. Fix the spelling, or remove the setting. Each shape page lists the settings it takes.
Related. METADATA_INVALID_VALUE
METADATA_INVALID_VALUE β
error Β· any node Β· active
Why. The setting is known, but its value can't be used: the wrong kind of value, a choice that isn't on the list, or text in the wrong format.
Code:
agentflow TB
connector github["GitHub"]@{ protocol: "http", url: "https://api.githubcopilot.com/mcp/" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read -.- github
end
The "protocol" setting on connector "github" can't be "http". Use "mcp".
The message names what is wrong. A wrong kind of value reads like this:
The "<setting>" setting on <shape> "<id>" should be text, not a number.Fix. Use a value of the kind the message asks for. The shape pages list each setting's values.
Related. METADATA_UNKNOWN_KEY, METADATA_REQUIRED
METADATA_REQUIRED β
error Β· input, connector Β· active
Why. Some settings have no default. A connector needs protocol and url, an input needs a trigger, and a schedule needs a cron or an at.
Code:
agentflow TB
connector github["GitHub"]@{ protocol: "mcp" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "List the open issues labelled bug." }
read -.- github
end
Connector "github" is missing its "url" setting. Add one.
Fix. Add the setting the message names.
Related. METADATA_INVALID_VALUE, METADATA_KEY_CONFLICT
METADATA_KEY_CONFLICT β
error Β· input Β· active
Why. A schedule runs either on repeat (cron) or once (at), not both.
Code:
agentflow TB
weekday[/"Weekdays at 09:00"/]@{ trigger: "schedule", cron: "0 9 * * 1-5", at: "2026-12-24T09:00" }
flow triage["Issue triage"]
read["Read issues"]@{ instruction: "Summarise every open issue." }
end
weekday --> triage
Input "weekday" has both a "cron" and an "at" setting, but a schedule takes only one. Keep "cron" to repeat, or "at" to run once.
Fix.
- Keep
cronto repeat. - Keep
atto run once.
Related. METADATA_REQUIRED