Can this issue be reproduced in a sandbox workspace? No since the device needs be to forced offline and then online.
Does this issue represent a regression? Did it previously work? Unknown
Description
If a device is online and an access code is updated, but then the device goes offline before Seam can confirm if the code was set, then the delay_in_setting_on_device warning and the failed_to_set_on_device error will not be set and the corresponding events will not be sent. If the device comes back online, then the errors and warnings are set.
Unknown if the same behavior applies to a newly created code, or only for the update case.
Steps to Reproduce
Create an access code.
Update the code, but then disconnect the device before the code is reported set.
Expected behavior:delay_in_setting_on_device warning and the failed_to_set_on_device error are set and events are sent.
Actual behavior:delay_in_setting_on_device warning and the failed_to_set_on_device error are not set and events are not sent.
Prerequisites
Description
If a device is online and an access code is updated, but then the device goes offline before Seam can confirm if the code was set, then the
delay_in_setting_on_devicewarning and thefailed_to_set_on_deviceerror will not be set and the corresponding events will not be sent. If the device comes back online, then the errors and warnings are set.Unknown if the same behavior applies to a newly created code, or only for the update case.
Steps to Reproduce
Expected behavior:
delay_in_setting_on_devicewarning and thefailed_to_set_on_deviceerror are set and events are sent.Actual behavior:
delay_in_setting_on_devicewarning and thefailed_to_set_on_deviceerror are not set and events are not sent.