starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 16:06:04 +03:00

[GH-ISSUE #2387] Add visibility into which bookmarks fail during import and why #1441

New issue

Closed

opened 2026-03-02 11:57:22 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 11:57:22 +03:00

Owner

Originally created by @LimitlessGreen on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2387

Describe the feature you'd like

Add detailed error visibility to bookmark import sessions.

Currently, when importing bookmarks, Karakeep only shows how many items succeeded and how many failed, but does not show which bookmarks failed or why.

Example:

There is no way to:

See which specific bookmarks failed
See the error reason (e.g. invalid URL, duplicate constraint, invalid HTML, missing data, etc.)

Requested feature:

For each import session, provide a way to view failed items
Show at least:
- URL (if available)
- Title (if available)
- Error reason

Possible forms:

"View failed items" button in the Import Session view
Expandable error list per session
Or a downloadable import log

Describe the benefits this would bring to existing Karakeep users

This feature would make bookmark imports:

Debuggable: Users can understand why imports partially fail instead of being blind
Trustworthy: Users can verify that their data was imported correctly
Fixable: Users can correct broken entries and retry only the failed ones
Scalable: Essential for large bookmark collections (hundreds or thousands of entries)

Measurable outcomes:

Fewer repeated failed imports
Less need to inspect server logs manually
Less data loss during migrations (e.g. from Linkwarden, browsers, or other tools)
Lower support/debug burden for both users and maintainers

Can the goal of this request already be achieved via other means?

Partially, yes.

Currently, the only way to get error details is by:

Inspecting server logs (e.g. docker compose logs)
Or splitting the import file into smaller chunks and trial-and-error testing

However:

This is not user-friendly
Not accessible to non-technical users
Not practical for large bookmark collections
And the UI itself provides no help or visibility

So while the information may exist somewhere in logs, the goal is not realistically achievable via the UI.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

Additional context

No response

Originally created by @LimitlessGreen on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2387 ### Describe the feature you'd like Add detailed error visibility to bookmark import sessions. Currently, when importing bookmarks, Karakeep only shows how many items succeeded and how many failed, but does not show which bookmarks failed or why. Example: <img width="837" height="522" alt="Image" src="https://github.com/user-attachments/assets/b197cc9e-f63e-4833-8c35-caddbcecd303" /> There is no way to: - See which specific bookmarks failed - See the error reason (e.g. invalid URL, duplicate constraint, invalid HTML, missing data, etc.) Requested feature: - For each import session, provide a way to view failed items - Show at least: - URL (if available) - Title (if available) - Error reason Possible forms: - "View failed items" button in the Import Session view - Expandable error list per session - Or a downloadable import log ### Describe the benefits this would bring to existing Karakeep users This feature would make bookmark imports: - Debuggable: Users can understand why imports partially fail instead of being blind - Trustworthy: Users can verify that their data was imported correctly - Fixable: Users can correct broken entries and retry only the failed ones - Scalable: Essential for large bookmark collections (hundreds or thousands of entries) Measurable outcomes: - Fewer repeated failed imports - Less need to inspect server logs manually - Less data loss during migrations (e.g. from Linkwarden, browsers, or other tools) - Lower support/debug burden for both users and maintainers ### Can the goal of this request already be achieved via other means? Partially, yes. Currently, the only way to get error details is by: - Inspecting server logs (e.g. `docker compose logs`) - Or splitting the import file into smaller chunks and trial-and-error testing However: - This is not user-friendly - Not accessible to non-technical users - Not practical for large bookmark collections - And the UI itself provides no help or visibility So while the information may exist somewhere in logs, the goal is not realistically achievable via the UI. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_

kerem

2026-03-02 11:57:22 +03:00

closed this issue
added the
feature request

status/untriaged
labels

kerem commented

2026-03-02 11:57:23 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Feb 8, 2026):

This is coming in the next release

@MohamedBassem commented on GitHub (Feb 8, 2026): This is coming in the next release

kerem referenced this issue

2026-03-02 11:59:21 +03:00

[PR #1441] [CLOSED] doc: add page detailling db structure and tables #1826

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#1441

No description provided.

Rows
Columns