Seam cannot create two access codes with the same code for different points in time

[seveibar]

Prerequisites

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

Description

You cannot create two time_bound access codes that share the same

Steps to Reproduce

1. POST /access_codes/create { device_id, code: "1234", starts_at: now(), ends_at: now() + ms("1d") }
2. POST /access_codes/create { device_id, code: "1234", starts_at: now() + ms("1w"), ends_at: now() + ms("1w") + ms("1d") } Returns a duplicate_code error

Expected behavior: Allow the creation of both codes

Actual behavior: Errors with duplicate_code

Additional Information

• https://hello-seam.slack.com/archives/C034Y5YQF0E/p1689008083315329

[itelo]

So, I could think of two possible solutions:

The first solution is the easiest one, make the second access code a not native schedule.

In the other one, we will need to add a new variable to know if we should schedule on the device or not.

[itelo]

After discussing with Seve and Ravi, we have come to a consensus that proceeding with this feature at the moment is not ideal. This is primarily due to the numerous edge cases that this feature entails.