The completed tasks and error messages provide useful information for testing and troubleshooting automations. However, it would be beneficial to include additional details such as the actual outcome and variable changes of decision/action blocks.
It could also be helpful if you could step through the logic or have breakpoints in automation test runs.
Hi @lpascoe -
Thank you for the feedback here! I will share with the team and they will follow up with any other questions for you about your request 
Thank you @lpascoe , and Beth for flagging! We’re actually in discovery on this feature now. Would you be open to a quick call to look at design prototypes, or to talk through your use cases? Thank you in advance, and also appreciate your taking the time to post here!
do you have any news on debugging Automations?
I really have trouble finding the cause, when an Automation suddenly starts to fail.
There is no way to know the last successful action or any other useful information.
I also found these related topics:
Debug automations - Support, Troubleshooting, & Help - Tulip Community
Debug usability in Automation Run History - Product Suggestions - Tulip Community
also:
Why is there no way to get informed, when an Automation fails?
I suddenly see in the run history, that it failed for a week or so and never got any information.
Since it stops when it fails, I also can not set up an eMail as error handling…