I made a submission earlier today. The first task "sizesCalc" was a "Hit" from the cache, but it took over an hour to do the cache-lookup according to the timing diagram (see attachment).
Workflow ID:851a6f6a-4589-4761-9652-9ce709af1999
Status:
Call Caching:Enabled
Submitted:April 14, 2017, 2:41 PM (1 hour ago)
Started:April 14, 2017, 2:41 PM (1 hour ago)
Inputs:Show
Outputs:None
Workflow Log:workflow.851a6f6a-4589-4761-9652-9ce709af1999.log
Workflow Timing:Show
Calls:
FilterWorkflow.sizesCalcHide
Call #1:
ID:
Status:Done
Cache Result:Hit
Started:April 14, 2017, 2:41 PM (1 hour ago)
Ended:April 14, 2017, 3:57 PM (4 minutes ago)
Inputs:Show
Outputs:Show
stdout:sizesCalc-stdout.log
stderr:sizesCalc-stderr.log
JES log:sizesCalc.log
I speculate that calls are queued and then looked up to see if there is a cache hit or a cache miss and that is the reason for the apparent 1.25-hour lookup.
Is this desired behavior?