I submitted a job (d730c1c3-4d60-44a6-9ba2-4f0a626f5070) on 10/23 and it failed at 15th tasks
I fixed the problem of the method, re-submitted the job using call caching along with two other workflows, but when I checked the job-manager after several hours, I found no "List View" tab.
When I looked into the google bucket of the submission, there was no folder for the workflow id under
I aborted the job and submitted the same job again (f5e9b09d-3f1e-470a-8483-7982d620d2c5), and
instead of starting from the 14th tasks which had been run successfully before, it started from beginning. In addition, the first 5 tasks were run successfully, but the workflow stuck there and did not advance.
Then I realized that all the past jobs I aborted were still displayed as "Aborting" and this made me suspect a possibility that this aborting is somehow affecting the call-caching. Is there a way to completely abort the jobs below?
Please sign in to leave a comment.