On the backend, the endpoint controller tries to create a whole new membership, which is expected from it:

Considering the fact that the email delivery is in the same endpoint, can't we do something like:

• Try to create a new membership
• If membership exists for given user, resend invite instead of throwing TEAM_INVITE_ALREADY_EXISTS exception.

Looking at the console API calls, this endpoint would be called only when a brand new membership is being created and when trying to resend an email, so this should be a viable fix. What do you think?

Edit: I would love to work on this issue 😁

I've seen the code and it seems like letting the code keep running on catching a Duplicate exception works.

Changed the code from this:

try { 
   $membership = Authorization::skip(fn() => $dbForProject->createDocument('memberships', $membership)); 
} catch (Duplicate $th) { 
   throw new Exception(Exception::TEAM_INVITE_ALREADY_EXISTS); 
} 

to this:

try {
    $membership = Authorization::skip(fn() => $dbForProject->createDocument('memberships', $membership));
} catch (Duplicate $th) {
    null;
} catch (Exception $th) {
    throw new Exception($th->getMessage());
}

I haven't been able to generate a case where an error actually gets thrown, so would appreciate feedback on the above approach!