My Workflows Page Displays No Workflows if Shared Endpoint Fails
See original GitHub issueBug Report
On develop branch, if the call to get shared workflows fails, then no workflows are displayed. The call to get the user’s workflows is cancelled.
The call to get the shared workflows was failing for me locally because the webservice was incorrectly making a call to SAM when the user wasn’t registered with Google. I will fix that as part of ga4gh/dockstore#1582.
But still logging this because I think combineLatest
here and/or here might need to be updated to handle error cases.
Also might want to consider displaying error messages for failing Ajax calls.
Just wanted to capture this in case this isn’t already in progress and deemed necessary.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Troubleshoot and diagnose workflow failures - Azure Logic Apps
How to troubleshoot and diagnose problems, errors, and failures in your workflows in Azure Logic Apps.
Read more >Server 2022.1 Release Notes - Alteryx Help
In WinAuth environments, the Public and Shared With Me tabs on the My Workspace page do not load when the owner of a...
Read more >Issues with publish workflows - Adobe Support
Find solutions for errors you receive trying to use the Share Online feature of Adobe XD.
Read more >Amazon Managed Workflows for Apache Airflow
This topic describes common issues and errors you may encounter when using Apache Airflow on Amazon Managed Workflows for Apache Airflow (MWAA) and ......
Read more >GitLab CI/CD `workflow` keyword
The workflow keyword is evaluated before jobs. For example, if a job is configured to run for tags, but the workflow prevents tag...
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
@garyluu Updated the description
Can confirm that this is working in the case that the sam path is set incorrectly, simulating SAM being down completely. Seeing indefinite waiting if SAM is blocked via AWS security groups, indicating that there might not be a timeout if SAM is up but non-responsive.
Will open a second lower-priority issue