I believe your solutions would help, but I don't think that would solve the issue.

There are tables with identity columns used by a 3rd party software that we cannot change.

So changing the identity to a trigger will not work for all tables in my databases.

This issue is affecting 4 different publications that contain about a dozen tables from 4 different databases.

Only the publications with tables that have identity fields are being affected.

Many of these tables are updated regularly and I could see those filling up the range and throwing the error.

But what is puzzling is that this message is showing for a table that does not have inserts/updates/deletes made against it.

This tells me that either something is configured wrong or there is a bug in the system.

I am continuing to see these errors show up constantly throughout the day with seemingly no provocation.

Any ideas on how to solve this?

Ben