# REST row-write API fails with error 1012 **URL:** \ **Category:** Bug Reports\ **Tags:** grid\ **Created:** [September 16, 2026, 11:06pm UTC](https://forum.appflowy.com/t/rest-row-write-api-fails-with-error-1012/5100 "2026-09-16T23:06:48Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PiBa](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.appflowy.com/piba/32/491_2.png) [@PiBa](https://forum.appflowy.com/u/PiBa)\ **Post date:** [September 16, 2026, 11:06pm UTC](https://forum.appflowy.com/t/rest-row-write-api-fails-with-error-1012/5100/1 "2026-09-16T23:06:48Z")
\*\*Hello, 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\*\* **Environment:** Self-hosted AppFlowy-Cloud v0.18.3, Seed license (id `ed0200d5-6ebc-4ec0-889c-d407ece4e725`, verified active, expires 2027-09-16, `max_users: 1`). Docker Compose deployment. **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: 1. `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"}`. 2. 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. 3. 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. 4. 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. Can someone help please ? Thank you ---
**Author:** ![Mayur](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.appflowy.com/mayur/32/17_2.png) [@Mayur](https://forum.appflowy.com/u/Mayur)\ **Post date:** [September 17, 2026, 2:15pm UTC](https://forum.appflowy.com/t/rest-row-write-api-fails-with-error-1012/5100/2 "2026-09-17T14:15:02Z")
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. ---
**Author:** ![Mayur](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.appflowy.com/mayur/32/17_2.png) [@Mayur](https://forum.appflowy.com/u/Mayur)\ **Post date:** [September 17, 2026, 2:28pm UTC](https://forum.appflowy.com/t/rest-row-write-api-fails-with-error-1012/5100/3 "2026-09-17T14:28:24Z")
I see that this is being tracked here and our team is already on it: > > > \### Bug Description > > \*\*Environment\*\*: Self-hosted AppFlowy-Cloud v0.18.3, Seed l…icense (id \`ed0200d5-6ebc-4ec0-889c-d407ece4e725\`, verified active, expires 2027-09-16, max\_users: 1). Docker Compose deployment. > > \*\*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: > > 1. \`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"}\`. > 2. 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. > 3. 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. > 4. 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. > > \### How to Reproduce > > // > > \### Expected Behavior > > // > > \### Operating System > > Ubuntu > > \### AppFlowy Version(s) > > Self-hosted AppFlowy-Cloud v0.18.3 > > \### Screenshots > > \_No response\_ > > \### Additional Context > > 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.