Skip to main content
Question

How to debug into sub taskbot


Forum|alt.badge.img+7
  • Navigator | Tier 3
  • 48 replies

hi team

when i running a tastbot A use debug mode, A called another bot B

how can i switch into bot B and continue debugging in it?

12 replies

Forum|alt.badge.img+7
  • Author
  • Navigator | Tier 3
  • 48 replies
  • March 25, 2022

the version is AA2019


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2693 replies
  • March 25, 2022

Hi @wang huadong​ ,

 

As of now we cannot jump from Master bot to Child bot and continue the shared debugging session. Its great idea though, kindly connect with your PEM or CSM, feel free to raise the Change Request to AA.


Ashwin A.K
Forum|alt.badge.img+8
  • Navigator | Tier 3
  • 2445 replies
  • March 25, 2022

Hi @wang huadong​ ,

 

I've been whining about this for quite some time now, and I'm glad that I'm not the only one who thinks this is a feature that the product team should look into.

 

Unfortunately, you have to debug the child bot directly.

 

Kind Regards,

Ashwin A.K


Forum|alt.badge.img+19
  • Most Valuable Pathfinder
  • 2693 replies
  • March 25, 2022

Even i am looking for this feature @Ashwin A.K​ , so you are not alone 😀


Forum|alt.badge.img+7
  • Author
  • Navigator | Tier 3
  • 48 replies
  • March 25, 2022

when i debug child bot directly, i must rerun it single, and set all the input variables manaually,

so trouble, wo....


  • Cadet | Tier 2
  • 1 reply
  • March 25, 2022

Hi @wang huadong​ 

 

Unfortunately, you cannot do that. However, Instead of using all the variables in the Child Bot, you can simply Run the Parent Bot inside the Child Bot and put the debugger.

 

Note: Don't forgot to disable child bot in Parent Task.

 

I know this is hectic, but doesn't give you pain to assign all the variables manually.

 

 

Thanks,

Javed Shaikh


Forum|alt.badge.img+5
  • Navigator | Tier 3
  • 19 replies
  • May 9, 2023

Hi, Adding to this thread - Has there been any development or movement on this?


LoganPrice
Most Valuable Pathfinder
Forum|alt.badge.img+12
  • Most Valuable Pathfinder
  • 77 replies
  • January 17, 2024

I am also adding to this thread. This would be a very nice feature to have. Debugging throughout the entire code is a standard feature in most IDE’s today, so it would make sense to have that for A360. Every one of our enterprise AA bots are at least two tasks deep, sometimes nesting to a third or fourth task level. Tracing errors back to source can be very challenging, and we currently rely on a mixture of message boxes and logging to do this, but it takes precious time.


Forum|alt.badge.img+4
  • Navigator | Tier 3
  • 10 replies
  • August 21, 2024

And one more to keep this one alive. It is silly to provide half a debugging tool. AA’s own best practices are to separate parent and child bots, so developers should then be armed with the proper tools to debug and test in this manner.


Forum|alt.badge.img+1

@JLogan2024  You can do this now:

 


Forum|alt.badge.img+4
  • Navigator | Tier 3
  • 10 replies
  • August 22, 2024

@laura.hotalling Thanks for this. I’ll have to check this out further I guess; I tried doing just that but it was not stepping into the child.


Forum|alt.badge.img+1

Id like to be able to set breakpoints in the child tasks. It’s annoying to start the parent, dig into the child, and then have to go line by line in the child task.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings