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.

Reference:

MuleSoft Composer Documentation

MuleSoft RPA Documentation