Refreshing a workflow that has become invalid does not update workflow
See original GitHub issueBug Report
Expected behaviour
When a workflow is changed to something invalid and then manually refreshed, I would expect it to get updated with verification problems displayed in the files tab. Another option is for an error message to display.
Actual behaviour
Refresh said successful, but nothing changed.
Steps to reproduce the behaviour
- Have a valid workflow with master/develop branch in my-workflows
- Modify it to say
class: CommandLineTool
in GitHub - Refresh workflow Notice the absence of any error indicators
┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.7 ┆Issue Number: DOCK-844 ┆Sprint: Seabright Sprint 16 Pram ┆Issue Type: Story
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Solved: When trying to update a Workflow Activity, I am ge...
When trying to update a Workflow Activity, I am getting the following error: Match not found, reset to original. Go to solution.
Read more >4 Workflow - Oracle Help Center
A Data Miner workflow is a mechanism to define data mining operations such as model build, test, and apply. These operations are defined...
Read more >Troubleshoot Project Online workflows - ProjectOnline
To create the view. From Project Web App, click on the gear icon then ** PWA Settings **. On the settings page, click...
Read more >Troubleshoot common workflow errors
In your HubSpot account, navigate to Automation > Workflows. Click the Workflows with errors tab. Hover over the workflow, then click Edit.
Read more >Notifcation: Couldn't update workflow · Issue #128 - GitHub
Steps to reproduce the behavior: Install the new version of Todoist workflow; Use keyword 'todo' and enter any letter; See error. Expected behavior....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@NatalieEO that’s good news I would try a few more scenarios (i.e. a valid workflow that becomes a malformed workflow in my-workflows, ditto for a malformed tool in my-tools, ditto for a malformed service in my-services) and if it all looks good. This can be closed
Ok, I think it was just a caching delay or something. Needed to wait a while before refreshing.