Closed yoHasse closed 8 months ago
@hartra344 - we need to update the default value we are setting here to be different for stateless workflows
This issue is stale because it has been open for 45 days with no activity.
Bump
This issue is stale because it has been open for 45 days with no activity.
Ping
This is something we're tracking on our backlog but would be a bit involved since we don't have the concept of stateful vs stateless where this is set. This likely won't be changing until later in the summer. Also moving this to the UX repo so we can respond when it's out
The default values are in the manifest, so when these manifests are sent by the backend apis it can set the value correctly, the client cannot conditionally set this based on workflow type since it is just a parameter value
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
❌ There was a problem linking to Azure Boards work item(s):
Please check the IDs and try again using the AB# syntax. Learn more
Describe the Bug
When creating a stateless workflow in the VS Code extension and then adding an Until loop it sets the Timeout value to PT1H as default. This is violating the maximum allowed time that a stateless workflow can run (5 minutes).
This results in some strange error messages and after some digging in the error logs I found the reference to that setting.
Plan Type
Standard
Steps to Reproduce the Bug or Issue
Workflow JSON
Screenshots or Videos
Additional context
No response
AB#16636564