@markusername yes, that might be the reason. It’s possible that Make is sending API requests and something is going wrong during row creation.
In such cases, the system attempts to create a new row and assigns it a unique ID, but if the process fails, the row isn’t fully created. However, Baserow still considers that ID as used. This is intentional and helps prevent ID duplication.
The same principle applies when multiple collaborators try to create rows at the same time — this mechanism (known as a race condition safeguard) ensures that two rows don’t end up with the same ID.
Since your table is connected to Make, it’s possible that some API requests are failing, which could explain the skipped numbers in row IDs.
Could you check the Make logs to see if there are any errors during those requests?