Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

RPA Start process is stucked

Ram_n Botelho
Tera Contributor

Hi.

First, I suffered to migrate RPA configuration from developer to QA instance. RPA configuration Process type received a new choice with value 3 instead of 1 (Unattended). I solved this using script.

 

And now I am stucked at the following message at Bot Process Job (sn_rpa_fdn_process_job).

 

"StartProcess request for the previous process job is in progress. The new process job that was triggered is skipped."

 

There is no other Process Job in the table.

2 REPLIES 2

Craig Gruwell
Mega Sage

Hi Ram_n Botelho,

 

Have you tried modifying the RPA Hub properties?

https://www.servicenow.com/docs/bundle/yokohama-integrate-applications/page/product/rpa-hub/referenc... 

 

2025-05-23_19-34-34.jpg

 

 

 

I tried to Force Start on Bot Process, not by Property.

I did not work.

Maybe there is a table to handle the bot queue and I could change the status of the record on the queue.