Table Error: Table Locks

Why does the Table Editor show "Temporarily Unable... modified recently"?

When you make a structural change to a table, TrackVia places a temporary lock on that table to prevent conflicting changes while the update is processed. Behind the scenes: the primary table is updated, its triggers are reinstalled, and a new history table is created for it.

Once that's done, you can go back to adding, updating, or deleting records in the table right away — but the lock itself stays in place until all of the table's history information finishes copying over to the new history table. If you see the "Temporarily Unable... it looks like this table was modified recently" message, it means that history-table copy process ("reconstitution") hasn't finished yet.

How long is this supposed to take?

It depends on how much history data the table has — a table with a large volume of historical changes will take longer to reconstitute than one with very little. There's no fixed expected duration.

When to escalate

As a rough guideline, if this lock is still in place after more than 4 hours, it likely means the reconstitution process failed rather than just being slow. At that point, self-service waiting won't resolve it — contact TrackVia Support.

Keep in mind 4 hours is a relative guideline, not a hard cutoff — it's based on typical data volumes, so a table with an especially large history could legitimately take longer. If you're unsure whether you're seeing normal processing or a stuck lock, it doesn't hurt to reach out to Support for confirmation rather than waiting indefinitely.