Sujet : Self-hosted Seed — new database collab objects never persisted to af_collab (plain pages/documents unaffected); REST row-write API fails with error 1012**
Symptom: Any database (Grid) created after the Seed license was activated (~2026-09-16) works normally in the web UI and stays in real-time sync on iOS, but:
POST /api/workspace/{workspace}/database/{database}/row always returns HTTP 200 with {"code":1012,"message":"user is not allowed to write Database {id}: permission target was not found"}.
The database object has no row in af_collab at all (SELECT * FROM af_collab WHERE oid = '{id}' → 0 rows), despite being fully functional/synced in clients.
A database created before the Seed activation (2026-09-15) has a normal af_collab row (partition_key = 1) and its row-write API works fine.
A brand-new plain document/page (not a database) created just now does persist correctly to af_collab (partition_key = 0, non-zero len) — so this is specific to database-type objects, not a general persistence regression.
What we ruled out:
License validity (confirmed active, periodically re-verified against billing successfully).
af_collab_member: manually inserted a Full access (permission_id 4) grant for the workspace owner on the affected database — no change.
af_workspace_owned_record_projection and af_workspace_group_view_permission: empty for both the working and the broken database — not the mechanism in play here.
Recreating the database from scratch: new object, same failure.
Duplicating the database via the UI (which should force full re-serialization): duplicate also has no af_collab row, same failure.
Restarting appflowy_cloud / appflowy_worker: no change.
Please help me understand the issue, Is it that you are not able to edit a database using REST API write calls? I will pass this along to our team, and hopefully someone can solve this for you.