Skip to main content
Question

Package version for session 'session' is different from parent bot

  • November 20, 2024
  • 3 replies
  • 197 views

Forum|alt.badge.img+3

I am getting this error with the Excel Advanced package. I have a bot that opens the file and then a subbot that is supposed to read the excel file using the global session created in the parent bot. Both bots have the same package version. When I run the bot while checked out it does not give the error, but when I check it in to public it throws the error every time. I have verified that the package version is the same multiple times and all packages are the default version. It was working previously and started throwing this error a few weeks ago and I cannot figure out why or what changed. Any idea why it would work when checked out or cloned but the exact same bot does not work when public?

3 replies

Forum|alt.badge.img+3
  • Author
  • Cadet | Tier 2
  • November 20, 2024

So I seem to have found a fix, if I check out the subbot and then immediately check it back in with no changes it works again. Not sure what broke it in the first place, but the process has several subbots that use the Excel session created in the top-level bot and every one of them is requiring this fix. 


Zaid Chougle
Navigator | Tier 3
Forum|alt.badge.img+17
  • Navigator | Tier 3
  • November 21, 2024

So I seem to have found a fix, if I check out the subbot and then immediately check it back in with no changes it works again. Not sure what broke it in the first place, but the process has several subbots that use the Excel session created in the top-level bot and every one of them is requiring this fix. 

Hey ​@jduncan , if it has been resolved then you can mark it as solved🖖🏻


Forum|alt.badge.img+3
  • Author
  • Cadet | Tier 2
  • November 25, 2024

 

So I seem to have found a fix, if I check out the subbot and then immediately check it back in with no changes it works again. Not sure what broke it in the first place, but the process has several subbots that use the Excel session created in the top-level bot and every one of them is requiring this fix. 

Hey ​@jduncan , if it has been resolved then you can mark it as solved🖖🏻

It is not resolved, I just found a fix. I need to know why it happened so I can prevent it in the future. For now all I can do is hope it does not happen again.