Skip to main content

Has anyone begun debugging child task bots yet?

 

If so, how did your team update the bot agents to the necessary version?

 

All our machines are stuck using bot agent 22.60.0 (required version is 22.60.23).

 

I’m on the development side (not a control room admin), so I don’t really understand how the agent update process works. Is this an automatic update pushed to A360 customers, or do our admins need to proactively do something to upgrade to agent version?

 

I am still using message boxes in child tasks to try and figure out what’s breaking in my bots. Cannot wait for the new debugger!

You may not be able to see if you have only a Bot Creator license, but the first place I would look is under Settings>>Devices>>Bot-agent Software. That will show what the CR Admin has selected for agent updates:

 If it is already set to auto-update, and yet you are not seeing new versions in a timely manner, I would check the Event Viewer on those machines to see if the agent is trying to install but failing for some reason.

You may not be able to see if you have only a Bot Creator license, but the first place I would look is under Settings>>Devices>>Bot-agent Software. That will show what the CR Admin has selected for agent updates:

 If it is already set to auto-update, and yet you are not seeing new versions in a timely manner, I would check the Event Viewer on those machines to see if the agent is trying to install but failing for some reason.

@JLogan3o13 thanks for the reply. I was able to get confirm with our Control Room Admin that we have “Auto-Update” selected.

Where is the event viewer? Is this another module viewed by CR Admins only? I can access the bot runner logs on my development device (C:\ProgramData\AutomationAnywhere\BotRunner\Logs) - would the error information be there?

Reply


Terms & ConditionsCookie settings