Chained TypeBot Link Block Does Not Return to Origin in Nested Flows
Hey,
I've identified an issue with the Link TypeBot block when attempting to chain three or more TypeBots. While a direct link between two TypeBots functions correctly, the return mechanism fails in a multi-level nested scenario.
1. Scenario 1: Two-Level Link (Working as Expected)
* Create TypeBot 1 and TypeBot 2.
* In TypeBot 1, use a Link TypeBot block to connect to TypeBot 2.
* Run TypeBot 1. Upon completion of TypeBot 2's flow, the conversation correctly returns to TypeBot 1.
2. Scenario 2: Three-Level Link or more (Bug Observed)
* Create TypeBot 1, TypeBot 2, and TypeBot 3.
* In TypeBot 1, use a Link TypeBot block to connect to TypeBot 2.
* In TypeBot 2, use a Link TypeBot block to connect to TypeBot 3.
* Run TypeBot 1. The flow proceeds from 1 to 2, and then from 2 to 3.
After TypeBot 3 completes its defined flow, the conversation should return to TypeBot 1, following the chain of parent-child relationships initiated by the Link TypeBot blocks. The implicit return (or stack unwind) from the linked bot should traverse back up the hierarchy.
When TypeBot 3 completes its flow, the conversation does not return to TypeBot 1. The execution effectively terminates after TypeBot 3, preventing the user from continuing the initial flow in TypeBot 1.
I've identified an issue with the Link TypeBot block when attempting to chain three or more TypeBots. While a direct link between two TypeBots functions correctly, the return mechanism fails in a multi-level nested scenario.
Steps to Reproduce:
1. Scenario 1: Two-Level Link (Working as Expected)
* Create TypeBot 1 and TypeBot 2.
* In TypeBot 1, use a Link TypeBot block to connect to TypeBot 2.
* Run TypeBot 1. Upon completion of TypeBot 2's flow, the conversation correctly returns to TypeBot 1.
2. Scenario 2: Three-Level Link or more (Bug Observed)
* Create TypeBot 1, TypeBot 2, and TypeBot 3.
* In TypeBot 1, use a Link TypeBot block to connect to TypeBot 2.
* In TypeBot 2, use a Link TypeBot block to connect to TypeBot 3.
* Run TypeBot 1. The flow proceeds from 1 to 2, and then from 2 to 3.
Expected Behavior:
After TypeBot 3 completes its defined flow, the conversation should return to TypeBot 1, following the chain of parent-child relationships initiated by the Link TypeBot blocks. The implicit return (or stack unwind) from the linked bot should traverse back up the hierarchy.
Actual Behavior:
When TypeBot 3 completes its flow, the conversation does not return to TypeBot 1. The execution effectively terminates after TypeBot 3, preventing the user from continuing the initial flow in TypeBot 1.
