Call caching not working reliably.

birgerbirger Member, Broadie, CGA-mod ✭✭✭

I ran a multi-task workflow on a sample pair yesterday. The workflow failed due to the Cromwell 34 upgrade. Several of the tasks in that workflow, however, had succeeded prior to the upgrade-induced failure. Today I relaunched the workflow, expecting hits in call caching for ALL those workflow tasks that successfully completed. That has not been the case. While one task got a call caching hit, most have not (the workflow is still running, but all but one of the completed tasks are reporting cache misses). An important use case of call caching is to be able to re-run a failed workflow and have Firecloud effectively pick up from that failure. This use case appears to be broken. Does call caching not carry over across Cromwell upgrades?

Best Answers

Answers

Sign In or Register to comment.