Professor
Yeah, we didn’t have that problem, but we did have an issue where our idempotent device adding script incorrectly attempted to add devices that were already present. I conclude that this is related. At the beginning of the script, it pulls the current list of all devices. For all devices in our SoR, it checks if the device already exists in LM. If it not in LM yet, the script attempts to add the device to LM.
During the timeframe in question, the script tried to add devices that were already present in LM. This means that the script thought the device was not in LM already, meaning that the device was not in the original GET request fetching all devices (which uses pagination so that’s not the issue). Without me doing anything, it started working a few hours later.
If the Azure discovery had the same problem, it would have thought the device was not already in LM, tried to add it and failed because it already existed, so it appended #1 and added it anyway.
