-
Notifications
You must be signed in to change notification settings - Fork 128
Description
Describe the bug
Based on the documentation, when I use the API to send a "batch of events" and the transaction_id is repeated and is not being ignored, the API returns an error saying that transaction_ids already exist.
{"status":422,"error":"Unprocessable Entity","code":"validation_errors","error_details":{"0":{"transaction_id":["value_already_exist"]},"1":{"transaction_id":["value_already_exist"]},"2":{"transaction_id":["value_already_exist"]},"3":{"transaction_id":["value_already_exist"]},"4":{"transaction_id":["value_already_exist"]}}}
Expected behavior
Endpoint should return 200 and just ignore any "transaction_id" repeated.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Version
- Lago: v1.17.4