Bug Description

On self-hosted AppFlowy Web 0.19.11, a database Grid view is replaced by the full-page error boundary. The heading is the component name "SomethingError". The banner is only "Something went wrong. Contact support if this keeps happening." (ACTION_PROBLEM), so the thrown error is not shown.

The database collab still loads. Two select fields have a type-option map and no content key:

• SingleSelect, type option "3": empty map
• MultiSelect, type option "4": empty map

Another SingleSelect (Status) still has type_option["3"].content and keeps its options. Row cells still store the option ids. The Board view of the same database still opens. The Grid field order lists only fields that exist.

parseSelectOptionTypeOptions in 0.19.11 returns { options: [] } when content is missing, so that parser does not throw. The Grid is still replaced by the error boundary.

How to Reproduce

How to Reproduce

1. Self-host AppFlowy Cloud with AppFlowy Web 0.19.11.
2. Open a database that has a SingleSelect and a MultiSelect whose type option holds only content, a JSON string {"disable_color":false,"options":[...]}.
3. Leave a tab of that origin open.
4. Read the database collab again. Those two content keys are gone and both maps are empty. A SingleSelect that was not touched can still have its string.
5. Open the Grid view of that database.
6. The page is the SomethingError boundary. IndexedDB af_database_cache can still draw the old chips. Putting content back while that tab stays open deletes it on the next sync. The same browser can keep showing the error after the strings are restored (React minified error ci: test web hook #321) until every tab of the origin is closed and site data for the origin is cleared. A fresh browser profile can open the same Grid URL.

Expected Behavior

The web client must not delete type_option content for SingleSelect or MultiSelect. A select field with no option list should show blank chips. The error page should show the exception, not the widget name "SomethingError" and not only the ACTION_PROBLEM sentence.

Operating System

macOS, desktop Chrome

AppFlowy Version(s)

AppFlowy Web 0.19.11 (appflowyinc/appflowy_web:latest, sha256:95c1a5df4f1318acef813bc22d32da9bdadd6de731edd2f59a42247ec98fc6f7, built 2026-10-13). Server image appflowyinc/appflowy_cloud:latest, sha256:0aa4b734a8b5660e28fe457e1939a5544eb707617b0ee44339090b8a63ae8bdf, container created 2026-10-14. The 0.19.11 web release note says the server must be at least 0.19.6.

Screenshots

Attach the Grid screenshot: heading "SomethingError", banner "Something went wrong. Contact support if this keeps happening.", and the paper-plane empty state.

Additional Context

The heading is hardcoded in src/components/error/SomethingError.tsx. getErrorMessage turns an unknown throw into ACTION_PROBLEM, which is the banner text. A field id that exists only in field_settings and not in field_orders was already present and is not this failure. This was seen twice on the same self-hosted workspace, 19 October and 20 October 2026.