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
Freida
9 months agoCarin
10 months agoHan
10 months agoTasia
10 months agoSerita
10 months agoFelicitas
10 months agoDaniel
11 months agoCruz
11 months agoBuck
11 months agoJacqueline
11 months agoJohnetta
11 months agoLanie
11 months agoMarkus
11 months agoArthur
11 months agoDorinda
11 months agoVerda
2 years agoTabetha
2 years agoAngelo
2 years agoHaydee
2 years agoYvonne
2 years agoKatina
2 years agoBrynn
2 years agoJoni
2 years agoRoyal
2 years agoYuki
2 years agoEleni
2 years agoMerilyn
2 years agoKanisha
2 years agoMarla
2 years agoDallas
2 years agoRosamond
2 years agoJoana
2 years agoDenise
2 years agoLyda
2 years agoBobbye
2 years agoBrett
2 years agoJina
2 years agoEdwin
2 years agoJina
2 years ago