# One, Two, Skip a Few...

DevFeed: [One, Two, Skip a Few...](<https://devfeed.tech/articles/one-two-skip-a-few-11941.md>)

Original publisher: [Read original article](<https://incident.io/blog/one-two-skip-a-few>)

Author: Pete Hamilton

Published: 2021-07-12T00:00:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [customer](<https://devfeed.tech/tags/customer.md>), [database](<https://devfeed.tech/tags/database.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>), [technology](<https://devfeed.tech/tags/technology.md>)

## AI overview

incident.io investigates why some customers saw unexpected jumps in incident identifiers. The article explains how per-organization Postgres sequences generate incident numbers and how transaction rollbacks can leave sequences ahead of the database records, while noting that this explanation appeared unlikely to account for the reported pattern.

## Source excerpt

The other day, we started getting strange reports from some customers of incident.io. Their incident identifiers -- unique numbers to identify each incident -- appeared to have jumped unexpectedly.