Log creating single malformed entry immediately following enrollment

[ChefAustin]

I'm seeing this occur on both the machines in front of me right now whereby after a device goes from unenrolled to enrolled, there seems to be a collision of write to the logfile which look like this:

Waiting for DEP record check...
Waiting foChecking mdm status - modern
MDM enrolled device 10.14.5
Checking mdm status - modern

Doesn't seem to be a big deal, and feel free to close this if it is a "Won't fix" sort of thing, just wanted to raise it before it forever fell out of the depths of my brainbucket.

[erikng]

I could have sworn I had a check where umad would only run one time and kill itself if the process was already running. That seems to indicate I didn't do that, or the check is now not working.