@phanTom It sounds like, given the options, save_object() would be the best option. How do you handle your calls to get_object in the parent playbook? Let's say I have 4 actions that use the result from get_object(). It seems like I would have to edit the code block for each of the 4 actions, to call get_object() and then use that object for the action call, which forces me to maintain callbacks for those 4 actions if I choose to make any changes to the playbook in the future. You can't use get_object() in the new custom functions, and legacy custom functions will be going away, so I don't know what other options I have.
... View more