IDC viewer starts up and fails with a file not found

[wlongabaugh]

We are seeing cases where the IDC viewer is launched from the portal, the Viewer starts up and immediately reports it cannot access the file. An example: https://(test-viewer-redacted)/1.3.6.1.4.1.14519.5.2.1.163047965868107465659169009295180558950.

When looking at the proxy report, we see a request:

https://(test-proxy-redacted)/dicomWeb/studies/1.3.6.1.4.1.14519.5.2.1.163047965868107465659169009295180558950/series/undefined/metadata

Note the "undefined" series ID, which returns a 404. This glitch clears when the viewer is reloaded. It is also the case that this happens randomly, implying a race condition on startup where a request is issued before the series is identified, and subsequent requests do not have this problem.