Lesson 6: Implementing Error-Handling in Rewst Workflows
Finish the workflow by implementing error handling, so it's prepared for situations where things don’t go as expected. This will help catch issues early and ensure smoother debugging.
Whatt to Eggs-pect
After completing this lesson, participants will be able to:
Build in "error handling" for a workflow by adding "on failure" transitions to actions
Implement feedback messages by using data aliases
Identify use cases for "Task Transition Criteria Sensitivity" on actions
Prerequisite(s)
In this lesson, we finish the "Add or Remove User - Microsoft Group" workflow. Make sure you've completed Lesson 5: Managing Workflow Paths before starting this lesson to ensure you're prepared for the next steps in the process.
Lesson Modules
To get started, select the first module. Each module includes a video and written guidance with resources, followed by navigation to go back/forward. To wrap up the lesson, visit Next Steps
Adding Error Handling to Workflow Actions (7 Minutes)
Lesson Resources
You can also find more information in our FAQ page: What does this error mean? "UnreachableJoinError: The join task|route "XXXXXXX" is partially satisfied but unreachable."
Next Steps
Complete the Knowledge Check and remember to Get Credit for your learning.
What Did You Learn?
Take a quick quiz and get instant feedback!
Get Credit
Submit this form to get credit for completing this lesson offline.
Keep On Cluckin'
We implemented error handling by adding feedback messages to notify us of the success or failure of our Graph and Exchange Online actions. We also briefly touched on the Task Transition Criteria Sensitivity setting, which will be covered in more detail in [lesson here].
In the next lesson, we'll wrap up by optimizing the workflow, streamlining the feedback messages to be sent directly to the person who filled out the form, and enhancing both the workflow's functionality and design.
Last updated
