Saumya Phor

@abdoulline We are now also seeing some failures in T0 Prompt processing jobs with similar symptoms. See - https://cms-talk.web.cern.ch/t/paused-job-in-promptreco-for-minimumbias-pd-run-378378/37744 - https://cms-talk.web.cern.ch/t/segmentation-violation-in-promptreco-for-minimumbias-pd-run-378382/37748

Here are the official GTs: - `140X_dataRun2_v2` - `140X_dataRun3_Prompt_frozen_v3` - `140X_dataRun3_v4` - `140X_dataRun3_PromptAnalysis_v2` The differences from the last GTs are below: [1] `run2_data`: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_dataRun2_v1/140X_dataRun2_v2 [2] `run3_data_prompt`: - https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_dataRun3_Prompt_v3/140X_dataRun3_Prompt_frozen_v3 - https://cmsconddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_dataRun3_Prompt_frozen_v1/140X_dataRun3_Prompt_frozen_v3...

> Just one question, in run3_data_prompt I see actually 2 differences for https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/140X_dataRun3_Prompt_frozen_v1/140X_dataRun3_Prompt_frozen_v3: Yes. The frozen GT update was missed in CMSSW autoCond at the time, but the Prompt GT...