Checklist

• I agree to the terms within the OpenFGA Code of Conduct.

Describe the problem you'd like to have solved

There are significant developer pain points when errors are received from the following operations:

• Writing a tuple that already exists
• Deleting a tuple that does not exist

Additional logic for error handling must be implemented to avoid or correct the situation, adding unnecessary complexity to client-side code and adding time required to complete operations due to retry scenarios.

Describe the ideal solution

OpenFGA v1.10.0 introduced support in the API for ignoring errors during duplicate writes (using the on_duplicate API property) and missing deletes (using the on_missing API property). The API solution is described in the OpenFGA roadmap item openfga/roadmap#79.

The SDK needs to add equivalent support. Refer to openfga/sdk-generator#610 for additional solution description.

Alternatives and current workarounds

No response

References

• Ignore Duplicate Writes roadmap#79
• [All SDKs] Add on_duplicate/on_missing options support for Write operations sdk-generator#610
• feat: duplicate writes (SQL only) openfga#2663
• feat: add support for Write API with on_duplicate and on_missing options api#233

Additional context

No response