Scans 17946 and 17944 have this problem. It seems only one has an actual error, so the other might have been cancelled before the error occurred. Given the error is stored after 'storing scan results' something else might be going wrong here. The UI says it's an api response issue. There are no exceptions recorded on or around May 8. Will have to continue investigating later.
Scans 17946 and 17944 have this problem. It seems only one has an actual error, so the other might have been cancelled before the error occurred. Given the error is stored after 'storing scan results' something else might be going wrong here. The UI says it's an api response issue. There are no exceptions recorded on or around May 8. Will have to continue investigating later.