PL-500 · Question #197
You create an automated workflow to run in unattended mode. The automation opens the customer relationship management (CRM) application to retrieve a list of unpaid invoices. The machine uses a…
The correct answer is A. Configure the On error behavior as Continue flow run and Repeat action. Configuring the On error behavior to Continue flow run with Repeat action allows the automation to retry the CRM open action until the VPN connection is fully established, handling variable connection delays.
Question
You create an automated workflow to run in unattended mode. The automation opens the customer relationship management (CRM) application to retrieve a list of unpaid invoices. The machine uses a virtual private network (VPN) to allow access to the CRM application. You observe that establishing a VPN connection sometimes takes 55 seconds or longer; therefore, opening the CRM application fails. You need to ensure that the automation consistently connects to the CRM application. What should you do?
Options
- AConfigure the On error behavior as Continue flow run and Repeat action.
- BCreate a condition.
- CAdd a Wait action after the run application action.
- DAdd a run application action into the On block error.
How the community answered
(22 responses)- A77% (17)
- B9% (2)
- C5% (1)
- D9% (2)
Why each option
Configuring the On error behavior to Continue flow run with Repeat action allows the automation to retry the CRM open action until the VPN connection is fully established, handling variable connection delays.
The 'Continue flow run' setting combined with 'Repeat action' instructs Power Automate Desktop to automatically retry the failed action rather than stopping execution, which directly addresses the timing issue where the VPN may not be ready within the first attempt. This retry mechanism keeps attempting the action until the VPN is established and the CRM application opens successfully.
Creating a condition checks a state at a single point in time but does not automatically retry the failed action, so it does not solve intermittent timing failures.
A fixed Wait action introduces an arbitrary delay that may be too short when VPN takes longer than expected, or wasteful when VPN connects quickly, making it an unreliable solution.
Adding the run application action inside an On block error handler can catch the error but does not implement a retry loop that handles the variable VPN connection timing.
Concept tested: Desktop flow error retry for timing-dependent actions
Source: https://learn.microsoft.com/en-us/power-automate/desktop-flows/errors
Topics
Community Discussion
No community discussion yet for this question.