Workflow errors caused by basename() call Completed
On Tuesday, September 28, 2021, some users have reported that their workflows are failing unexpectedly.
We believe that this is due to a change in basename() that causes filenames to be incorrectly constructed in task outputs. This currently only affects String-type inputs provided to basename().
Workflows using basename() with String-type inputs are expected to perform incorrectly at this time, we are working to revert these changes.
Our engineers are aware of this issue and are currently working on a fix.
Comments
1 comment
We've taken remediation steps that we believe should resolve the issue. If you are still experiencing this issue, please let us know.
Please sign in to leave a comment.