
Adam Nichols
- Total activity 42
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 1
- Subscriptions 7
Activity overview
Latest activity by Adam Nichols-
Adam Nichols commented,
Hi Jett, We identified and fixed a bug that caused the "relaunch failures" feature to fail unexpectedly with the "Error 400: Invalid input" message when the workflow's method name contained the p...
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Hi Luda, We identified and fixed a bug that caused the "relaunch failures" feature to fail unexpectedly when the workflow's method name contained the period character. Regular (initial) submissions...
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Hi folks, It looks like we've inadvertently created a situation where part of the application is accepting periods in method names, while another part rejects them. We apologize for this inconsiste...
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Hi Adam - thanks for your post. While it definitely looks like something is going wrong with your workflow, the "key not found" error is not present so I would suggest that you make a new thread.
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Hi Justin - thank you for the feedback, we apologize for the inconvenience.
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Hi James - thank you for the feedback, and apologies for the inconvenience.
- View comment
- Adam Nichols
- 1 vote
-
Adam Nichols commented,
-
Adam Nichols commented,
Hi GE, You have repeatedly posted with great confidence about what you think the root cause is. The team developing the product has access to considerably more information, such as Cromwell interna...
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
Sorry, we do not have an ETA. Your options are to: Wait until the issue with Docker Hub images passes Use images from GCR, Quay, or another repo – users report a 100% success rate after migrating
- View comment
- Adam Nichols
- 0 votes
-
Adam Nichols commented,
No additional cost, the tasks exit in the normal amount of time and do not incur any more expense than usual. The still-running status is simply an artifact of the workflow status failing to update.
- View comment
- Adam Nichols
- 0 votes