Activities become invalid when package version changes

Some of the activities are becoming invalid when the package version changes (going to higher version). Shouldn’t they be working on package update?
only way to fix is by re-building the error ones as it doesn’t allow to copy-paste from older version of project as well.

Hi @priya.pai,
Sometimes newer package consist of completely re-build schema for the activity and data used for the old one are incompatible with new schema. That’s why they become invalid and you need to place it again (in newer version) and provide needed data and attributes once again. I would say it works as designed.

1 Like

Hi,
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.

1 Like

Hello @priya.pai,

Do you have a specific package in mind?

Cant recollect the package, but mainly been facing issues with simple things such as multiple assign, snippet for Delays etc.

1 Like

Hello @priya.pai,

Normally, we guarantee backwards compatibility. That is, even if you use a newer Studio/Robot, you will still be able to Run the workflow as is.
What we can’t offer is Forward compatibility. Every once in a while, there are underlying changes that will make a specific activity package to not be compatible But starting with a specific version of Studio. In which case, you will get an Unresolved activity in the Workflow.
These situations are rather rare though and usually quite specific.
Next time it happens, please write down the Activity/Package Version/Studio Version and we will check it out.

1 Like

Sure, will do

1 Like