Hi,
I run into the following issue intermittently in that after failure, a few resubmissions will eventually get the Flow to work. With that said, can you recommend how to troubleshoot or what the issue may be?
Flow Background:
This is the third Flow in a solution that I have implemented for onboarding new users to our organization. The other two have work fine especially leading up to this Flow's execution for onboarding the employee. Before this condition is a series of steps parsing a Planner Task body to obtain a supervisor's email, set as String variables leading up to this. Additionally, there is a Universal Principle Name (UPN) that is provided by our organization's IT team that feeds into the 'Search for users (V2)' task to get the employee's details. From there, the flow forks by sending an email to the employee (right) and hiring manager (left). The employee pathway works 100% of the time when this error occurs, but the hiring manager's pathway errors out more often than not. Are there any suggestions on how to troubleshoot?
One thing that I am wondering if it impacts the flow is the '\n' new line that is indicated by the error for the value in the email field. Maybe when I am indexing the Task Planner details for the supervisor's email, I am going two (2) indexes too far?
Share
Report
All responses (
Answers (
532
