on 2021 Jun 16 8:27 AM
Hi everyone,
I was trying to use the "Trigger as a new job" funtionality on a subautomation in a for each loop. Somehow after deploying and executing the bot in attended mode the automation marked as "Trigger as a new job" was simply skipped. It was like it didn't even exist within the automation.
I followed Simon Rabourg's OpenSAP video: https://open.sap.com/courses/rpa5/items/1ffAd8Cz8cIIBtrcBf1yhZ
and the documentation which is difficult to understand: https://help.sap.com/viewer/8e71b41b9ea043c8bccee01a10d6ba72/Cloud/en-US/ff2bde5df1b743eca91ed2ba13b...
The automation I created is supposed to do a SAP Help search online for certain keywords that are stored in an excel file. The searching step is supposed to run in parallel.

While starting the webpage I also enabled bEvenIfExist so that the browser windows can be opened parallely.
Why was the subautomation skipped?
Request clarification before answering.
Hi larshep,
The documentation is outdated. Link will be updated soon.
The trigger as a new job cannot be executed in Test mode.
When you add an Attended mode for your main BOT, there should be another agent ( VDI or any other available machine)in unattended mode to execute your sub automation.
When you check the Logs in Factory,you will be noticed that your subautomation is in queue and is waiting for available desktop agent in unattended mode to execute it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Link for updated documentation.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.