Not Unique (409)
The Not Unique error occurs when the client attempts to create or update a resource with an identifier that is not unique. This error typically arises in situations where different resources cannot have the same name. For instance, creating a pipe through API with a name that already exists in the profile will result in a Not Unique error.
Possible Causes
- Attempting to create a resource within Langbase with an identifier (e.g., username, email, ID) that already exists in the system.
- Updating a resource within Langbase with a value that violates a unique constraint, such as trying to assign an already-used identifier.
Troubleshooting Steps
- Check Existing Records: Verify that the identifier being used (e.g., username, email) is not already in use.
- Use Different Identifier: Use a unique identifier that is not already in use.
Recommendation
Make sure to always use unique names for your pipes and memory to avoid this error. If you encounter this error, check the existing records and use a different identifier to resolve it.