Can this issue be reproduced in a sandbox workspace? No
Does this issue represent a regression? Did it previously work? No
Description
On August integration, we encountered an issue where the device could not be set up due to an invalid format. In such cases, we set an error message and add a delay before attempting to set the code again. However, since the error is related to the code format, the setup will fail indefinitely, leaving the customer clueless about why their code is not being set. We need to handle this situation properly, so that the user is informed about the issue and can either try to update the code format or contact the support team for assistance.
An error message that explain to the user that he should try to update the code.
Actual behavior:
The error message does not indicate that the error is caused by an invalid code format, so the user will never try to update it, and the code will never be set.
Prerequisites
Description
On August integration, we encountered an issue where the device could not be set up due to an invalid format. In such cases, we set an error message and add a delay before attempting to set the code again. However, since the error is related to the code format, the setup will fail indefinitely, leaving the customer clueless about why their code is not being set. We need to handle this situation properly, so that the user is informed about the issue and can either try to update the code format or contact the support team for assistance.
https://hello-seam.slack.com/archives/C041U284Z5K/p1710937530990829
Steps to Reproduce
Expected behavior:
An error message that explain to the user that he should try to update the code.
Actual behavior:
The error message does not indicate that the error is caused by an invalid code format, so the user will never try to update it, and the code will never be set.