HeartbeatProbe outputs in the ecc_queue are set to Processed, when they were not processed because the MID Server is down - Known Error

HeartbeatProbe outputs in the ecc_queue are set to Processed, when they were not processed because the MID Server is down Description HeartbeatProbe outputs in the ecc_queue are set to Processed, when they were not processed because the MID Server is down.

This causes confusion when investigating MID Server down events.

Steps to Reproduce

On a new Utah or earlier instance Install a MID Server somewhere Shut it down Wait >10 minutes You will see an ecc_queue output record for topic=HeartbeatProbe set to state=Processed It was clearly not processed by the MID Server, which is not running Actual behaviour: The scheduled job MID Server Monitor, using script include MonitorMIDServer, sets missed outputs to misleading Processed state.

Expected Behaviour: Outputs should only ever be set to processed if a MID Server has run the probe, and returned an input. Then the business rule "ECC Queue - mark outputs processed " is what sets it to processed, which is the only thing that should be doing this. It should be set to Error state instead.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.