This happens for an automation that currently runs in published version. I upgraded all dependencies to latest version and now these activities fail because the Folder Path is blank.
It used to be that blank folder path meant that the activity used the folder path of the current automation. This doesn’t work.
How do I get around this without having to revisit every step and hard code the path?
I have many automations and all will need to be re-published due to a change in a shared library version. Having to fix all empty folder path fields will be a big job.
