Repository navigation
Log task rejections without a traceback - #1192
Open
DavidMStraub wants to merge 1 commit into
Open
DavidMStraub wants to merge 1 commit into
DavidMStraub wants to merge 1 commit into
Conversation
TaskRejection marks 4xx outcomes such as the AI agent exceeding its usage limits. Celery logged them at ERROR with the full chained traceback. Declaring them in Task.throws logs them at INFO without one, while the result backend still stores the failure for the client.
DavidMStraub
force-pushed
the
quiet-task-rejection-logs
branch
from
November 19, 2026 09:14
c7038db to
e613073
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expected 4xx outcomes inside Celery tasks, such as the AI agent exceeding
LLM_MAX_REQUESTS, were logged at ERROR with a full chained traceback. This filled the worker logs.TaskRejectionalready marks these outcomes as expected, and Sentry already ignores it. This PR addsthrows = (TaskRejection,)toContextTask, which is Celery's setting for expected errors:TaskErrors still log at ERROR with their traceback.Tests cover both log levels.