Hi @polion6,
Welcome to the Google Cloud Community!
It seems you’re encountering an issue with Playbook’s restriction against loops, making it challenging to return from child playbooks (B and C) to the main playbook (A).
Here are some possible solutions to help you with your scenario:
- Use Status Indicators and Conditional Routing: To avoid loops, instead of directly invoking Playbook A within Playbook B, set a status indicator in Playbook B. Then, use conditional routing in Playbook A to handle the flow based on the status indicator set by Playbook B.
- Design a Centralized Summary Function: Ensure that the main Playbook (A) is responsible for summarizing all collected parameters. Child Playbooks (B and C) should focus solely on their specific tasks and set their status indicators upon completion.
For more detailed information regarding crafting examples and best practices for Playbooks, you can refer to this documentation.
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.