Capturing Warnings With Workflow Continuing

[default_7]

Hello, I've got a bit of a head scratcher with this one. When it comes to capturing errors inside my workflow, I use the 'On error' function inside the the actions that will create a variable with the error message I need and then run a sub-workflow to send an email with the error. These are treated as failed and the workflow can't carry on.

However, I also need to capture warnings in the same way my current workflow is capturing errors as above, with using the 'On error' function create a variable of the warning then run a sub-workflow to put that warning variable in a txt file so later then go back to the point of when it failed and carry on. What makes it more difficult is there couple be multiple warnings so I can't use the same variable as it will be overwritten. Hence why it is placed in a txt file  for every waring that is captured.

An example of what I'm trying to do is, when entering a form online there are required text fields. If the automation workflow can't enter in a required field then it will error as it can't progress on. But if it can't enter in other fields that are not required, I need to capture what fields can't be entered but still carry on with the workflow as it is not critical. 

Hopefully that all makes sense. Any help or ideas would be really helpful. Thank you 🙂

[Deenuji]

@default_7 

When utilizing the "on error" feature, you can append your warnings to a text file and choose the "Go to next action" option to continue the flow's execution. This approach ensures that instead of halting at the occurrence of an error, the workflow will log your warnings into the text file and proceed to the next action.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

[default_7]

Thank you for your solution, unfortunelty that method still doesn't work for me. I've got a workaround my issue by naming the warning variable 'N/A' at the start of the workflow. Then after each action that could have a warning, have a if statement to check that variable name, if it doesn't contain 'N/A' capture the error then reset that variable back to N/A to capture any more warnings.