It can happen that instead of both a target and config kind deviation resource existing, only the target kind exists, and this one then toggles on every deviation sync period (30s) between showing configuration paths which are not yet covered by any config resource, and deviations detected on the device.
Perhaps this is caused by a failure to create the config deviation (and the missing resource when trying to update the deviation list causing it to use the target deviation resource), but in this case, the target resource should not contain deviations from a config snippet, and should instead be handled elsewhere