The owner-scoped to global claims migration ran its RENAME, CREATE, INSERT and DROP in autocommit, so an interruption after CREATE left the new table empty, orphaned the rows in the legacy table, and never re-triggered. Wrap the rebuild in an explicit transaction so a crash rolls back cleanly and the migration re-runs on the next boot. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| mcp_servers_db.py | ||
| providers_db.py | ||
| rag_db.py | ||
| research_runs_db.py | ||
| studio_db.py | ||