Congatudo does not find segments if there are maps pending to be saved

[ciltocruz]

Hello.

Sometimes, when the conga automatically goes out to do a cleanup and, for whatever reason, it detects that the map could have changed (when it's not the case, but there were things in the way anyway and it went crazy)

So in the application what I show you in image 1 appears. The issue is that as long as I do not assign YES or NO to the newly detected map, the remaining automations no longer work. This is the error that the log spits out:

[ERROR] MQTT: Error while handling MapSegmentationCapability/clean/set {
  payload: '{   "segment_ids": [ "12" ],   "iterations": 1 }',
  error: Error: Segment ID does not exist, or map was not loaded: 12
      at PropertyMqttHandle.setter (/snapshot/app/backend/lib/mqtt/capabilities/MapSegmentationCapabilityMqttHandle.js:48:35)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
}

I'd say it's more than the "map hasn't loaded". Does anyone know if there is a way to prevent this from happening? Thank you!

To Reproduce

Cause your conga to detect a map change. Next, clean up a segment. I do it with home assistant + MQTT sending the segment id to be cleaned.

Screenshots

Vacuum Model

Conga 4090

Congatudo Version

2023.05

Expected behavior

That, despite detecting a map change, it does not remain as if the map had not loaded and respects "the previous one".