Notifications
Clear all
How To
8
Posts
3
Users
0
Reactions
4
Views
Topic starter
I am utilizing Telegram to initiate a workflow. However, when I attempt to invoke another workflow using the "Execute Workflow" node within callin.io, the process halts. The trigger functions correctly, and callin.io receives the data, but the execution phase gets stuck.
I've confirmed that the workflow ID is accurate, as everything functions as expected when I use the "Execute a Sub-Workflow" node instead of the "Execute Workflow" tool. The child workflow is configured to accept all incoming data.
I also experimented with a setting, specifically enabling "Save Manual Executions", but this did not resolve the issue.
Additionally, the logs show the error: Workflow execution had an error
Cannot read properties of undefined (reading ‘execute’)
main workflow
Error:
main workflow without call workflow tool - i think it isnt problem with the rest
and i talk that block works (execute workflow) so its the prove that only tool (call workflow) doesn’t work
child workflow
Thank
Information on your callin.io setup
- callin.io version: 1.93.3
- Database (default: SQLite): SQLite
- callin.io EXECUTIONS_PROCESS setting (default: own, main): I’m running callin.io on Railway and haven’t changed the
EXECUTIONS_PROCESSsetting, so it’s using the default:own - Running callin.io via (Docker, npm, callin.io cloud, desktop app): Railway
- Operating system: Windows
Posted : 19/05/2025 4:17 am
Hello,
This kind of error typically indicates that the AI Agent Tool is attempting to invoke the workflow but lacks the necessary information to send, or is missing the required inputs.
In your “Call Workflow Tool” configuration, the sub-workflow is configured to accept all data, however, the Agent still requires specific instructions on what data to transmit.
Kindly attempt the following:
-
Navigate to your child workflow
- Ensure the initial node is “When Executed by Another Workflow” (this is already in place, which is good).
- Within that node, modify the Input data mode from: “Accept all data” to “Define input structure”.
- Subsequently, define the precise fields (e.g.,
query,productName, or whatever your tool is intended to receive).
-
Update the Tool description
-
In your “Call callin.io Workflow Tool”, use a description such as:
“Call this tool to search for information on Wikipedia. It requires a string field named ‘query’.”
-
-
Incorporate a system message or an example with your AI Agent
-
Something along the lines of:
“When the user requests a lookup, utilize the ‘WikipediaSearch’ tool and provide a field named
query.”
-
When you select “Accept all data”, the Agent is unsure what data to send. However, by defining a clear input structure, you provide the Agent with a framework to operate within, thereby preventing the undefined error.
Let me know if this resolves the issue!
Posted : 19/05/2025 4:42 am
Topic starter
Hello, I've tried this, and it appears to be the same as before with no changes. When I run the workflow, nothing is displayed. Typically, nodes turn red when there's an issue, but mine just shows "executing workflow" as if it's thinking. I might have made a mistake, but here are some screenshots:
Posted : 19/05/2025 1:46 pm
You could attempt to add a 'do nothing' node to the workflow that's being invoked by the tool. Have you checked the past executions of the workflow being called? It might also be beneficial to try pinning the data by editing within the workflow.
Posted : 19/05/2025 4:44 pm
Topic starter
Hi there, as I understand it, I added a 'do nothing' node to my subworkflow. In the executions within the subworkflow, nothing appears, and it remains the same. Also, when I pinned something, it froze as usual.
Posted : 19/05/2025 5:00 pm
Topic starter
I'm not sure if this will help, but I ran the same program on a different host, and it worked. Why might that be? And how can I fix the issue on my main host?
Posted : 19/05/2025 5:35 pm
Topic starter
Okay, I understand now. My mistake! I restarted the host, and it's working. Thanks for all your help!
Posted : 19/05/2025 5:41 pm
Ah, that's great!
Yes, a good old restart often resolves many issues, aha!
Posted : 19/05/2025 6:13 pm