Discovery Schedule stuck with Skipped sensor for Horizontal Pattern because of error in payload: Payload length XXXXXXX exceeded limit of 5000000 - Support and Troubleshooting

Discovery Schedule stuck with Skipped sensor for Horizontal Pattern because of error in payload: Payload length XXXXXXX exceeded limit of 5000000 Issue Discovery Schedule gets stuck with Skipped sensor for Horizontal Pattern because of error in payload: Payload length XXXXXXX exceeded limit of 5000000.

The devices thus do not complete discovery. Release All Cause discovery.max_payload_size parameter is available for all probe types. Specifies the maximum string length of Discovery probe results that the MID Server sends to the instance. The MID Server verifies the size of the Discovery probe results before sending them to the instance. If the Discovery probe results exceed the limit, the MID Server discards them and returns a warning message.

Resolution This applies only to probes where the Used by Discovery field is true, or Used by Orchestration is true (e.g. for Windows - Powershell probe) mid.discovery.max_payload_size

Type: integer (bytes) Default value: 5000000 Set the above probe parameter to a higher value than the number (XXXXXXX) in the error message.(Skipped sensor for Horizontal Pattern because of error in payload: Payload length XXXXXXX exceeded limit of 5000000)

Please note with this change , payload limit is increased from default 5 MB to the assigned value and allow payloads up to defined size to be sent to the instance. Discovery should now be completed with out the Skipped sensor for Horizontal Pattern because of error in payload.