Hello Everyone,
I am using the package Browser Automation ,
I create a child bot using the variable type session for output; But when I call the child bot in parent bot and trying to use the session output in other browser action . I have the following message Field 'sessionName' must not be null.
The child bot run succesfully but I think the session output is not well return even the session Id is not null
Best answer by Bot Dev
I am able to use within parent bot too, global session should be global:
Check package version and bot compatibility version in your parent task.
Check if any local session with same name exists.
Try to create a fresh parent task and test, seems to work for me.
+10I think you discovered your own answer. Those sessions don’t persist across bots. Certain kinds of sessions, for example in the Excel Advanced package, can be shared.
Hello
The browser automation persist accross bots because the first time , I run the bot it works all the day and at the end it stop working. If I create a new taskbot with same actions, at the beginning it works before having this error message
+10Your best bet is to keep all browser functions within the same task bot.
For the issue, share the screenshot of error, at which step do you encounter error, Run task bot ?Then it seems to be issue with run task variable mapping. Drag and drop new run task and try with different name of variables.
For the package and workaround:
Update your package to latest version if possible, which will also allow you to select window by title.
Hello
I use same package version is used across parent and all child tasks for session to work. 3.1.2-20240227-221641
I use now global session values
I encounter this error after the run task bot action
I do not see any error message in the screenshot, just the activities.
Field 'sessionName' must not be null.
I was able to pass from child to another child via global session.
Check if you are initializing and passing session properly.
Parent:
Child1(Starts session):
Child2(Uses this session):
Ensure you are not using “End Session” anywhere in between which could be closing the session.
If I use a second child bot ; it works. So the problem is we cannot use the session directly in the parent bot .
The green is the second child bot , it works
The red is when i use directly action browser automation
I am able to use within parent bot too, global session should be global:
Check package version and bot compatibility version in your parent task.
Check if any local session with same name exists.
Try to create a fresh parent task and test, seems to work for me.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
