[Bug] Publishing and duplicating database record pages fails when they contain linked database views
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with the reported backend entry points: libs/appflowy-cloud-publishing/src/api/workspace/publish.rs, libs/appflowy-cloud-publishing/src/biz/workspace/publish_asset_rewriter.rs, and libs/appflowy-cloud-pages/src/pages.rs near line 1237. Reproduce by publishing and duplicating a database record page with a linked database grid, then compare with a page containing a regular inline grid. Done means both actions succeed while preserving the linked view behavior.
Written by the indexing model from the issue text.
Description
Bug Description
Publishing or duplicating an individual database record page fails when the page contains an inline linked database grid view referencing an existing database elsewhere in the workspace.
The problem is specific to linked database views. Normal inline grids created directly within the page work correctly.
The issue is reproducible with newly created database records and is not limited to older or migrated records.
How to Reproduce
-
Create a database named Company.
-
Create a second database named Opportunities.
-
Add records to both databases.
-
Open an individual record within Company as a full page.
-
Insert a linked database grid view referencing the existing Opportunities database.
-
Attempt to publish the individual Company record page from AppFlowy Desktop.
-
Observe Error 1017.
-
Attempt to duplicate the same Company record page.
-
Observe the invalid-request error.
-
Remove the linked database grid view from the Company record
-
Attempt publishing again.
Result: Publishing succeeds after the linked database view is removed.
The problem also occurs with newly created records, making legacy record corruption an unlikely explanation.
Expected Behavior
Expected Behavior
An individual database record page containing a linked view of another database should:
Publish successfully and generate a publicly accessible page.
Preserve or correctly render the linked database view in the published page, subject to supported publishing behavior.
Allow the parent record page to be duplicated without returning an invalid-request error.
Actual Behavior
When attempting to publish a database record page containing a linked database grid:
Publishing error:
We couldn't publish this page.
Error 1017: We couldn't confirm whether this action finished. Check the result before trying again.
Operating System
Windows 11
AppFlowy Version(s)
0.15.0
Screenshots
No response
Additional Context
Database Relationships
The actual environment contains:
A
Companydatabase.An
Opportunitiesdatabase.Individual Company records containing embedded linked views of Opportunities.
Opportunities records that may contain relationships to entries in other databases.
It has not been determined whether additional database relationships contribute to the issue.
The consistent failure condition is the presence of an embedded linked database grid view.
Backend Investigation
1. Publishing Requests Return HTTP 200
Nginx access logs show multiple publishing requests returning successful HTTP responses.
Example:
POST /api/workspace/{workspace_id}/publish HTTP/1.1
200 133Despite these responses, the AppFlowy desktop client displays Error 1017.
This suggests the problem may involve application-level processing, response handling, or publishing-result verification.
2. AppFlowy Cloud Processes Publishing Requests
The backend logs show publishing requests reaching the following components:
appflowy_cloud_publishing::biz::workspace::publish_asset_rewriter
appflowy_cloud_publishing::api::workspace::publishExample log entries:
Extracted 1 file references from document ...
Rewrote document assets for view_id=..., found 1 blob keysThese entries indicate that AppFlowy Cloud begins processing publishing operations.
No definitive publishing exception has been correlated with Error 1017.
3. Missing Parent View Errors
AppFlowy Cloud also reports errors involving missing parent database views.
Example:
RecordNotFound(
"parent view ... not found in workspace ..."
)Source:
libs/appflowy-cloud-pages/src/pages.rs
line_number: 1237Handler:
post_page_database_view_handlerAPI endpoint:
POST /api/workspace/{workspace_id}/page-view/{view_id}/database-viewThese errors may be related to linked database view handling, but a direct causal relationship with the publishing or duplication failure has not yet been confirmed.
4. Relevant Source Code Paths
The backend logs reference:
libs/appflowy-cloud-publishing/src/api/workspace/publish.rs
libs/appflowy-cloud-publishing/src/biz/workspace/publish_asset_rewriter.rs
libs/appflowy-cloud-pages/src/pages.rsAreas worth investigating:
Linked database view resolution during publication.
Serialization and snapshot generation for database record pages.
Handling of source database and linked view identifiers.
Duplication of pages containing embedded linked database views.
Desktop publishing-result verification when the backend returns HTTP 200.
Impact
This issue prevents publishing individual Company database records that contain linked views of related Opportunities.
Linked database views are important for account management workflows because they allow users to display related records without duplicating the underlying data.
Removing these views restores publishing functionality but removes important contextual information from the page.
The issue also prevents duplicating affected database record pages.
Current Workaround
Remove the embedded linked database view before publishing or duplicating the page.
This is not a practical permanent workaround because the linked database view is required for normal workflows.
Regular independent inline grids do not trigger the problem.
Additional Findings
AppFlowy Desktop version:
0.15.0AppFlowy Cloud version:
0.20.4Docker services are running and healthy.
The publishing API returns HTTP 200.
Publishing works for normal pages and database entries without linked views.
New records reproduce the problem when a linked database view is added.
Removing the linked view restores publishing and duplication.
No Nginx publishing timeout was identified in the captured logs.
These findings suggest a reproducible issue in linked database view handling rather than a general infrastructure or authentication problem.
.
- Dominant language
- Dart
- Stars
- 79.1k
- Forks
- 6.3k
- Avg merge
- 17h 29m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AppFlowy-IO/AppFlowy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9118 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AppFlowy-IO/AppFlowy#9094 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9075 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppFlowy-IO/AppFlowy#9074 ·
Maintainers usually reply within 1 day
All issues in AppFlowy-IO/AppFlowy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dreautall/waterfly-iii#890 · 1 comment ·
Maintainers usually reply within 1 day