starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 07:56:05 +03:00

[GH-ISSUE #2336] More control and transparency over failed jobs #1419

New issue

Closed

opened 2026-03-02 11:57:10 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @Yasand123 on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2336

Describe the feature you'd like

Would be nice to be able to:

See the exact jobs that failed (crawling, inference, etc.) Like a list showing each job individually.
Re-attempt selected jobs, or cancel specific jobs.

A bonus would be able to also see what jobs are being processed/are unprocessed and optionally cancel one or more of them.

Describe the benefits this would bring to existing Karakeep users

Currently you can only "Reattempt for all failed", this is ambiguous because the user doesn't know which items failed, especially when more than one did. Even then, you might not want to reattempt all of them. Maybe you've already manually fixed tags on one item and want to cancel it, but reattempt another.

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

Not that I can see.

Have you searched for an existing open/closed issue?

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

Additional context

I apologize if this was requested, I searched for the terms that came to mind but couldn't find similar posts.

Originally created by @Yasand123 on GitHub (Jan 2, 2026). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2336 ### Describe the feature you'd like Would be nice to be able to: 1. See the exact jobs that failed (crawling, inference, etc.) Like a list showing each job individually. 2. Re-attempt selected jobs, or cancel specific jobs. A bonus would be able to also see what jobs are being processed/are unprocessed and optionally cancel one or more of them. ### Describe the benefits this would bring to existing Karakeep users Currently you can only "Reattempt for all failed", this is ambiguous because the user doesn't know which items failed, especially when more than one did. Even then, you might not want to reattempt all of them. Maybe you've already manually fixed tags on one item and want to cancel it, but reattempt another. ### Can the goal of this request already be achieved via other means? Not that I can see. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context I apologize if this was requested, I searched for the terms that came to mind but couldn't find similar posts.

kerem

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

closed this issue
added the
feature request

status/untriaged
labels

kerem commented

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

Author

Owner

@redge76 commented on GitHub (Feb 3, 2026):

I got 713 unprocesses items but I don't know what is wrong.
There is no re-enqueue "unprocessed items" in the list of available actions and I'm not sure that to regenerate ai tags for all bookmarks is a good idea. (at least not cost efficient...)

@redge76 commented on GitHub (Feb 3, 2026): <img width="400" alt="Image" src="https://github.com/user-attachments/assets/7c3a286a-65c7-4aa7-8b05-e89f601f897b" /> I got 713 unprocesses items but I don't know what is wrong. There is no re-enqueue "unprocessed items" in the list of available actions and I'm not sure that to regenerate ai tags for all bookmarks is a good idea. (at least not cost efficient...)

kerem commented

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

Author

Owner

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

@redge76 in the nightly build you can re trigger processing only for unprocessed bookmarks. I'm also revamping the entire import process for better visibility (PR will be merged today)

@MohamedBassem commented on GitHub (Feb 3, 2026): @redge76 in the nightly build you can re trigger processing only for unprocessed bookmarks. I'm also revamping the entire import process for better visibility (PR will be merged today)

kerem commented

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

Author

Owner

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

This has been merged and will be available in the next release

@MohamedBassem commented on GitHub (Feb 8, 2026): This has been merged and will be available in the next release

kerem commented

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

Author

Owner

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

Thank you Mohamed.

@Yasand123 commented on GitHub (Feb 8, 2026): Thank you Mohamed.

kerem referenced this issue

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

[PR #1419] [MERGED] Fixed json syntax error #1815

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#1419

No description provided.

Rows
Columns