An RPA process is invoked by a MuleSoft Composer flow. The RPA process has a User Task that can take up to 24 hours to complete.
When an RPA process involves a User Task that can take a significant amount of time (up to 24 hours) to complete, it is best to use a follow-up mechanism to handle the results once the process is finished:
Second MuleSoft Composer Flow:
Create a second MuleSoft Composer flow that is triggered when the RPA process completes. This ensures that the first flow is not held up while waiting for the long-running RPA process to finish.
The second flow can start based on an event, such as the completion status of the RPA process, ensuring timely and efficient processing of the results.
Trigger Mechanism:
Configure the RPA process to notify MuleSoft Composer when it is complete, possibly using a REST API or another integration method.
Best Practices:
This approach adheres to best practices by keeping flows modular and focused on specific tasks, making them easier to manage and troubleshoot.
MuleSoft Composer Documentation
MuleSoft RPA Documentation
Verda
22 days agoHaydee
7 days agoYvonne
24 days agoKatina
28 days agoJoni
22 hours agoRoyal
7 days agoYuki
12 days agoEleni
1 months agoDallas
9 days agoRosamond
12 days agoJoana
17 days agoDenise
1 months agoLyda
25 days agoBobbye
30 days agoBrett
1 months agoJina
1 months agoEdwin
2 months agoJina
2 months ago