I am using Autopilot to trigger an RPA process that creates Action Items in Action Center. The Autopilot waits until the action item is created, but it does not wait for the action item to be assigned and completed.
However, in Orchestrator, the process shows a “Suspended” (On Hold) status. I have already used the “Wait for Form Task and Resume” activity in my workflow, but still, Autopilot proceeds without waiting for the task to be completed in the Action Center.
How can I make Autopilot wait until the Action Item is completed in the Action Center before continuing?
@Ajith_Pandi_T You can split the process in 2 part anyways you can trigger part 2 after completing action as you are running the process in attended mode
Hi @Darshan_Sable , Thanks for you reply - here our goal is for Autopilot to wait until the Action Center task is completed before continuing, without requiring a second process or additional trigger - (User’s Single Prompt From Autopilot)
Persistence activities are something of a speciality of mine, so I’d be happy to try to advise here.
I don’t really use Autopilot that much though so need some more information there.
Can you show us what happens in Autopilot? Does the process end up failing at the suspension point?
It would not surprise me if autopilot cannot handle long running workflows.
I believe maestro is what you need to use so that the tasks are created and it waits..as autopilot is not for waiting but would call series of tasks and proceed further
I’d be very interested to hear if Autopilot can wait on stuff in Maestro, but it cannot wait for traditional RPA, cause from what I know they both just appear as normal jobs.
Not saying you are wrong, it would just be weird to me based on what I think I know of how some of this stuff works, so if someone can demonstrate it indeed works with Maestro but not with normal RPA I’d love to see the demo for my own understanding.
I thought you meant that autopilot could start a Maestro job and correctly wait for it to finish even though it also needs to suspend several times for human in the loop and robot in the loop tasks to finish.
Sounds like all of us are unsure exactly what should be possible, I don’t have the time right now to dedicate to testing, but if someone from this thread does I’d love to see the results.
after few rounds of testing and checking with multiple options
Wait for resume tasks will not make auto pilot wait
Instead create a separate task and expose to autopilot so it checks if those activities are complete or send any notification after resume and ask auto pilot to check it can
and all of this makes sense as autopilot works on request and response type …so waiting is not part and also while testing I felt yes it should not wait as well..because autopilot is like a chat interface and if you hang it up then then purpose of it is defeated
As the maestro task was running we could check the status by asking auto pilot to check..anyways the status is getting updated back in the job log of autopilot but it would still continue even when task is running
