ERROR? Automatic number assigned multiple times

I have an interesting case that has only arisen in the last few weeks.

In one of our databases on SeaTable.io, several automatic numbers were assigned a second time this month. Numbers were “recycled” that were assigned for the first time about a few months ago.

I have noticed three cases so far. But due to the large number of entries and the fact that it is not possible to query this case using a filter, there could well be or become more.

In our case this is not critical as these numbers are only used for communication purposes and we do external referencing in other ways - but maybe someone is using the ID as a real external reference! You should be vigilant in this case.

Thanks for this hint. We will have a closer look at this.