When I try to debug an automation activities like Get Asset and Download from storage bucket fail

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.

@Phillip_Duncan

At the bottom right corner, make sure you are changing the folder to the folder in which you have the specified assets and storage bucket.

2 Likes

Hello @Phillip_Duncan

It should work as you describe (with empty paths).

Can you confirm that the required assets are present in the exact folder from which the job is running?

Regards
Soren