You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ethan-conrad1 May 24, 2024
When calling the Kimai API to retrieve timesheet entries, in some scenario's we are getting duplicated results returned. For example:
As can be seen in the above images, the API request is the same, with the only difference being the page number. However, we are receiving the same id (9760) in both pages.
The issue seems to always be going from page 1 to page 2. If we change from page 2 to page 3 there are no issues.
This is causing uniqueness constraint violations in our application that uses the API.
Please can this be looked at?
The text was updated successfully, but these errors were encountered:
Discussed in #4875
Originally posted by ethan-conrad1 May 24, 2024
When calling the Kimai API to retrieve timesheet entries, in some scenario's we are getting duplicated results returned. For example:
As can be seen in the above images, the API request is the same, with the only difference being the page number. However, we are receiving the same id (9760) in both pages.
The issue seems to always be going from page 1 to page 2. If we change from page 2 to page 3 there are no issues.
This is causing uniqueness constraint violations in our application that uses the API.
Please can this be looked at?
The text was updated successfully, but these errors were encountered: