Basically Parent bot is what you build ideally to hold just the high level flow and trigger points.

Each trigger point is a child task, there can be sub child tasks as well.

Example

Parent Task - Initiate variables, *Call Open Webpage task , Return Pass or Fail , If Fail do something , else do something , *Call Database task ..

* marked becomes your Child Tasks

There is no set rule, but they correlate like connected with wires(in form of variables)

Parent task can have a variable for URL which is passed to child task , means child task must have that URL variable too - This is correlation.

@Claudia Jimenez Acosta​ :

if you are still facing an issue then please create a support case

How to create a support case :

https://apeople.automationanywhere.com/s/article/How-to-create-a-support-case-in-service-cloud

if you don't have access to the above link, email the AA Support team "apeopleopsteam@automationanywhere.com" to get access.