You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we re-trigger a sequence run in Sequence Hub (Base Space) with same sequencing data (RunInfo.xml ), it may has same instrumentRunId (instrumentRunId is set by the RunInfo.xml).
This may cause combination of different runs, and as the run id and apiUrl is not updated, the run details and sample sheet api call will be failed.
So rather than using instrumentRunId as the unique identifier, run 'id' should be a better choice. And in early stage of bssh events when run files are still uploading, there is no instrumentRunId set.
The text was updated successfully, but these errors were encountered:
When we re-trigger a sequence run in Sequence Hub (Base Space) with same sequencing data (RunInfo.xml ), it may has same
instrumentRunId
(instrumentRunId is set by the RunInfo.xml).This may cause combination of different runs, and as the run
id
andapiUrl
is not updated, the run details and sample sheet api call will be failed.See example in dev: https://orcaui.dev.umccr.org/runs/sequence/seq.01JN2WW3887X8BH3P6NMPWVPRD

events compared:
So rather than using
instrumentRunId
as the unique identifier, run 'id' should be a better choice. And in early stage of bssh events when run files are still uploading, there is noinstrumentRunId
set.The text was updated successfully, but these errors were encountered: