orphaned operation ID, in the context of timeout....is it a known issue?

@khal

consider this operation ID operations/EPe8-cr_KhjGluSduevM0Xcg_eDe0bUCKg9wcm9kdWN0aW9uUXVldWU

I find its exec.sh to find the workspace ID, submission ID, and workflow ID :

wm8b1-75c:script esalinas$ gcloud alpha genomics operations describe operations/EPe8-cr_KhjGluSduevM0Xcg_eDe0bUCKg9wcm9kdWN0aW9uUXVldWU|ggrep -Pi 'exec'
        cmd: /bin/bash /cromwell_root/exec.sh
          path: exec.sh
        name: exec
        exec: gs://fc-80a44a23-fb19-43fe-be5c-b315f71da471/e90d2ec6-890c-4d1b-a21e-e4365199c0ff/CallingGroupWorkflow/f6730d17-d177-442e-bff5-0f16e46e051a/call-CallSomaticMutations_131_Prepare/exec.sh

Using the workspace ID I find the workspace name and namespace

wm8b1-75c:script esalinas$ /usr/local/bin/fissfc space_search -b fc-80a44a23-fb19-43fe-be5c-b315f71da471
rebc_controlled_access/rebc-oct16

I navigate in the UI to the workspace and the submission, and find a single workflow ID (6e8c....) which is NOT the workflow ID from the exec URL (f673....). (see attached). Most workflow had a timeout error. This indicates that the job is an orphan. An operation ID is defined to be an orphan if it is not displayed in the monitor tab under the workflow. In this case the workflow does not show up because of the timeout error, so I consider this operation ID an orphan.

Is the timeout issue seen here a known issue?
Are orphans from timeouts a known issue?
Note that the submission is from Oct 24th, 2016 nearly 6 months ago. That submission time may mean that this is might be from a cromwell before 24