Why is it possible to create duplicated tenancy check?

[abrahamseni]

I am able to create more than one tenancy check with the same checkTypeId. Is this intended?

The context is this tenancy ID - WNL240036 (env: SAV) created duplicate checks on May 17. We are still investigating it, but this has never happened before. Looking at the created timestamp, it only differs about 2-3 seconds. Do you have any idea what is happening?

Thanks.

Specification

• Project: Reapit.Services.Tenancies
• Read my comment below. This can be confirmed by looking at the gateway logs and observing the two different users calling the API at the same time
• Handling this properly is probably best done by using a unique index. This then puts the onus on the database to ensure there's never any duplication. PL to raise with AC engineering team.

[plittlewood-rpt]

Hi @abrahamseni I've had a look at our logs and there was a really high volume of calls related to tenancy checks for this tenancy on 17th May (384 between 10.23 and 13:46). It looks like two users were looking at tenancy checks for this tenancy on the app at exactly the same time (let me know if you need to know who the users were). It's likely that different instances of the API handled requests from each user, and a race condition may have occurred where both instances thought that the checks didn't exist, so both created them.

[abrahamseni]

Thanks @plittlewood-rpt I'll talk to the user and see how we can handle the issue.

[plittlewood-rpt]

Logged internal issue for engineering spike (ENG-125)