Hey Marius,
Thanks for the tips. Here’s what I tried and how they turned out:
- Using an absolute path didn’t work, it didn’t even register it as a full path, it thought it was a relative path so it threw this error:
And yes, the file exists in the folder in the right path with the right name. I’ve been working with dynamic paths before so I know they used to work. - I tried moving the file to a non-OneDrive folder and it still threw the same error.
3)I don’t have any antivirus installed so I doubt that could’ve caused it. I only have Windows Defender, and the workflow I’m trying to invoke isn’t PowerShell related, nor does it have persistence activities in it. - bej is just a dummy variable that I used to test this. It literally just contains “Bejerman” in it.
What’s interesting about this issue is that it’s not a runtime error. It throws out the exception after checking for validation errors, so I’m guessing something changed in the process with the latest Studio Update. Should I flag this as a potential bug?
Thanks,
Matias