Replies: 2 comments
-
Here Alternative way for use terminal or any programming language output on workflow |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I am running about 20 workflows that using powershell core as an script that running in action. For example:
to set output parameter I was using:
but just now I receive an error:
What I can do about it ?
P.S. All other workflows using this command and work flawlessly. I want to know what happened on this workflow so it start fails on this command
P.S.S. I guess it is a bug because other workflows that was running early today start to fail on this line with exact error message... What going on ?
Beta Was this translation helpful? Give feedback.
All reactions