FlowiseAI/Flowise · error · Error
Execute Flow node name is required!
Error message
Execute Flow node name is required!
What it means
Each Execute Flow sequential node requires a display name; the name is slugified (lowercased, spaces to underscores) into the LangGraph node identifier. Thrown at init when inputs.seqExecuteFlowName is empty.
Source
Thrown at packages/components/nodes/sequentialagents/ExecuteFlow/ExecuteFlow.ts:154
const searchOptions = options.searchOptions || {}
const chatflows = await appDataSource.getRepository(databaseEntities['ChatFlow']).findBy(searchOptions)
for (let i = 0; i < chatflows.length; i += 1) {
const data = {
label: chatflows[i].name,
name: chatflows[i].id
} as INodeOptionsValue
returnData.push(data)
}
return returnData
}
}
async init(nodeData: INodeData, input: string, options: ICommonObject): Promise<any> {
const selectedFlowId = nodeData.inputs?.selectedFlow as string
const _seqExecuteFlowName = nodeData.inputs?.seqExecuteFlowName as string
if (!_seqExecuteFlowName) throw new Error('Execute Flow node name is required!')
const seqExecuteFlowName = _seqExecuteFlowName.toLowerCase().replace(/\s/g, '_').trim()
const startNewSession = nodeData.inputs?.startNewSession as boolean
const appDataSource = options.appDataSource as DataSource
const databaseEntities = options.databaseEntities as IDatabaseEntity
const sequentialNodes = nodeData.inputs?.sequentialNode as ISeqAgentNode[]
const seqExecuteFlowInput = nodeData.inputs?.seqExecuteFlowInput as string
const overrideConfig =
typeof nodeData.inputs?.overrideConfig === 'string' &&
nodeData.inputs.overrideConfig.startsWith('{') &&
nodeData.inputs.overrideConfig.endsWith('}')
? JSON.parse(nodeData.inputs.overrideConfig)
: nodeData.inputs?.overrideConfig
if (!sequentialNodes || !sequentialNodes.length) throw new Error('Execute Flow must have a predecessor!')
const baseURL = (nodeData.inputs?.baseURL as string) || (options.baseURL as string)
const returnValueAs = nodeData.inputs?.returnValueAs as string
View on GitHub (pinned to abe4a8601a)
Solutions
- Enter a unique, non-empty name in the 'Execute Flow Node Name' field.
- Avoid duplicating another sequential node's name in the same flow (the slugified id collides in the graph).
Defensive patterns
Strategy: validation
Validate before calling
const name = (nodeData.inputs?.seqExecuteFlowName ?? '').trim()
if (!name) throw new Error('Provide an Execute Flow Node Name before init') Prevention
- Make the name field required in your chatflow authoring checklist.
- Ensure slugified names are unique across the flow.
When it happens
Trigger: The 'Execute Flow Node Name' parameter was left blank when the node was added or edited.
Common situations: Newly added node saved before naming; name field cleared during an edit; programmatic chatflow build omitting the field.
Related errors
- Execute Flow must have a predecessor!
- LLM Node name is required!
- Custom function must have a predecessor!
- End must have a predecessor!
- Invalid flow ID: must be a valid UUID
AI-assisted analysis of FlowiseAI/Flowise@abe4a8601a (2026-08-12).
Data as JSON: /api/errors/45e96e2737e7f61c.
Report an issue: GitHub.