Issue: During the cloud discovery, probes/patterns get stuck in the processing state for a long time and discovery will not run successfully, instead it gets canceled.
If you look at the below images, discovery is getting stuck only when the mid server - MID_CORE is used for processing. All the other payloads are processed successfully by the other mid server - MID_DISCO1. So when MID_CORE is involved, the discovery gets stuck and finally gets canceled.
The issue might be due to some issue in the mid server - MID_CORE which is why it is not able to process the payload.
As a workaround, let's say if you are performing an Azure cloud discovery, remove the Azure capability from the problematic mid server. So when discovery is triggered, the problematic mid server will be excluded and discovery runs successfully.
