DB primary key increment flurries

[mhsdef]

There exists an unknown state that causes the incidents primary key to rapidly increment dozens or more times.

Eg:

• Last breaking is 742.
• Next breaking opened by the bot is 784.

I've seen this happen, so far, twice in operation. Nothing obvious in the logs. No orphan records created in the table.

[mhsdef]

Two thoughtlines so far:

• We create incidents in a transaction so, maybe something repeatedly invokes that causing a bunch of rollbacks in succession -- incrementing the table's pk but no actual creations.
• Janky SQL driver and/or Drizzle ORM. Pure conjecture, but, I don't trust either of them much. Something along this line might compound into that rollback situation.

[mhsdef]

In theory, the txn rollbacks should be logging errors though.... 🤔