data_source in_trash: true not reflected in Trash UI (API/UI inconsistency)

[swotvibe]

Summary

We are observing an API/UI inconsistency when trashing Notion data_source objects. The API correctly reports data_source objects as in_trash: true, but these items do not appear in the Notion Trash UI.

Environment

• Notion API Version: 2026-03-11
• SDK: @notionhq/client (latest)
• Affected Objects: data_source objects (6 items verified)

Reproduction Steps

1. Use Notion API version 2026-03-11
2. Trash a data_source via API by setting in_trash: true using the Update a data source endpoint
3. Retrieve the same object again via API
4. Confirm the object is returned as:
   • object: "data_source"
   • in_trash: true
5. Open Notion UI and check Trash

Actual Result

The API reports the data_source as in_trash: true, but the item does not appear in the Trash UI.

Expected Result

One of the following should be true:

1. Trashed data_source objects should appear in Trash UI in a user-visible way, OR
2. The documentation should explicitly state that trashed data_source objects are not exposed through the standard Trash UI

Analysis

Based on the official Notion API model:

• A database is now a parent of one or more data sources
• data_source is a first-class object in the current model
• The 2026-03-11 upgrade makes in_trash the canonical trash field across pages, databases, blocks, and data sources
• The "Update a data source" endpoint explicitly supports updating whether a data source is "in the trash"
• Notion Help Center describes moving data sources to Trash from the UI
• Audit log documentation includes events such as "Data source restored from trash" and "Data source permanently deleted"

Because of this, in_trash: true on a data_source should represent a real trashed state, not just a cosmetic flag.

Possible Explanations

The current behavior suggests one of these:

1. UI inconsistency: Trashed data_source objects are real but not surfaced in Trash UI
2. Undocumented product limitation: data_source trash state exists in the API but is not reflected in the standard Trash UI
3. Regression: How data_source trash state is mapped between API and UI

Verification

We verified 6 affected items. All 6 objects:

• Are returned by the API as object: "data_source"
• Have in_trash: true
• Do not include a data_sources array (confirming they are actual data_source objects, not database containers)

Request

Please clarify whether this is:

1. Expected behavior
2. A documentation gap
3. A product bug in Trash UI handling for data_source objects

Concise Conclusion

This does not look like "the API failed to trash the item." It looks more like "the API successfully trashes data_source objects, but the Trash UI does not display them consistently or does not document that behavior."