Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: failed jobs showing stale information in "Error" tab after manual retry #862

Closed
itay-davidson opened this issue Dec 18, 2024 · 4 comments · Fixed by #886
Closed

BUG: failed jobs showing stale information in "Error" tab after manual retry #862

itay-davidson opened this issue Dec 18, 2024 · 4 comments · Fixed by #886

Comments

@itay-davidson
Copy link

When I manually retry failed jobs in my and they fail again, the information shown in the "Error" is that of the first retry, not that of the latest.

This can be quite frustrating as not all jobs have proper logs, and it leaves me with no choice other than checking my app logs which is time consuming.

Error information should probably be that of the latest retry, or maybe an aggregation of all tries.

@felixmosh
Copy link
Owner

Hi, thank you for reporting this issue.

Bull-board doesn't saves any Queue or Job state, this means that it takes the data avilable on the queue each request.
Which means that probably bull / bullmq has this issue.
Can you try debugging it?

(do the entire flow from within you app, and get the failed job...)

@ahnwarez
Copy link
Contributor

ahnwarez commented Jan 3, 2025

@itay-davidson, I just wanted to clarify: Are the stack traces displayed in the Error tab for a given job listed from oldest to newest, requiring you to scroll all the way down to find the most recent error? And are you suggesting that the most recent errors should be displayed from top to bottom?

I can confirm that stack traces are displayed oldest to newest.

@felixmosh
Copy link
Owner

felixmosh commented Jan 30, 2025

@ahnwarez will you make a PR for the sorting issue?

@ahnwarez
Copy link
Contributor

@felixmosh Absolutely. I'll start working it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants