cromwell Configuring Call Caching验证记录

call-caching {

  enabled = true

  # In a multi-user environment this should be false so unauthorized users don't invalidate results for authorized users.
  invalidate-bad-cache-results = true

  blacklist-cache {
     # The call caching blacklist cache is off by default. This cache is used to blacklist cache hits based on cache
     # hit ids or buckets of cache hit paths that Cromwell has previously failed to copy for permissions reasons.
     enabled: true

     # All blacklisting values below are optional. In order to use groupings (blacklist caches shared among root
     # workflows) a value must be specified for `groupings.workflow-option` in configuration and the workflows to
     # be grouped must be submitted with workflow options specifying the same group.
     groupings {
       workflow-option: call-cache-blacklist-group
       concurrency: 10000
       ttl: 2 hours
       size: 1000
     }

     buckets {
       # Guava cache concurrency.
       concurrency: 10000
       # How long entries in the cache should live from the time of their last access.
       ttl: 1 hour
       # Maximum number of entries in the cache.
       size: 1000
     }

     hits {
       # Guava cache concurrency.
       concurrency: 10000
       # How long entries in the cache should live from the time of their last access.
       ttl: 1 hour
       # Maximum number of entries in the cache.
       size: 20000
     }
  }
}

在该配置下，有任务运行完成后，重新提交但只有第一步没有重复运行， 其余后续步骤都重新调度运算，和预期不符合。