
Announcements
I have 2 flows with parent/child relationship.
The child flow is configured to :
- perform scan of SP folder for new files
- retrieve contents of those files, including a key value
- perform lookup of the key value in an existing Excel file (Master)
- if key exists, appropriate entry in the Excel file (Master) will be updated with the file contents
- if key does not exist, contents will be added into a seperate Excel file (Temp)
- once everything has been processed, a string variable will be updated and value returned to parent flow
To perform the check for key value, I employed scopes :
- initial scope to check for key value
- if initial scope fails, update the Excel file (Temp)
- if scope above is skipped (meaning key value is found), update Excel file (Master)
- this entire process is nested in a "Apply to each" action, to go through each new file detected
I tested this with several files, one of which contains errors. Predictably, the flow failed due to the invalid file, but all other files were processed successfully. However, when I checked on the Excel files, seems that the actions associated with the successful files had been processed multiple (7 times).
Error received was that child flow had failed due to 'timeout'. Observed that while child flow had failed, parent flow was still 'running', expecting feedback. I had expected flow to fail due to the invalid input/processing, not via timeout. Based on the behavior, it seems to me like parts of the flow are being retried.
I tried changing the retry policy for actions in the child flow to "None", but issue persists. Changed the retry policy for the parent flow action "Run Child Flow" to None as well without success.
Have no idea what is going on. Please advise, thanks.