Schlage code conversion emits `access_code.unmanaged.failed_to_convert_to_managed`, but the access_code eventually converts to managed

[seveibar]

Prerequisites

• Can this issue be reproduced in a sandbox workspace? No
• Does this issue represent a regression? Did it previously work? Unknown

Description

Converting a schlage code sometimes emits access_code.unmanaged.failed_to_convert_to_managed, but the code is successfully later converted.

Steps to Reproduce

1. POST /access_codes/unmanaged/convert_to_managed { access_code_id }
2. ??? Reproduction Unclear
3. Receive access_code.unmanaged.failed_to_convert_to_managed
4. Access code later appears as managed

Expected behavior: The access code should remain unmanaged if it fails to convert, or become managed and not emit access_code.unmanaged.failed_to_convert_to_managed

Additional Information

• https://hello-seam.slack.com/archives/C041U284Z5K/p1688554318303689