-
Notifications
You must be signed in to change notification settings - Fork 16.6k
Fix KeyError when accessing retry_delay on MappedOperator without explicit value#56605
Merged
kaxil merged 3 commits intoapache:mainfrom Oct 15, 2025
Merged
Fix KeyError when accessing retry_delay on MappedOperator without explicit value#56605kaxil merged 3 commits intoapache:mainfrom
kaxil merged 3 commits intoapache:mainfrom
Conversation
Member
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
INFO: 172.18.0.1:47834 - "GET /api/v2/dags/example_dv_simulation_flow/tasks/run_simulation HTTP/1.1" 500 Internal Server Error
ERROR: Exception in ASGI application
raise ResponseValidationError(
fastapi.exceptions.ResponseValidationError: 1 validation errors:
{'type': 'get_attribute_error', 'loc': ('response', 'retry_delay'), 'msg': "Error extracting attribute: KeyError: 'retry_delay'", 'input': , 'ctx': {'error': "KeyError: 'retry_delay'"}}
cc: @kaxil , @vatsrahul1001
...licit value
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
Member
|
@dheerajturaga Was the issue you saw on main or 3.1.0? Would be good to add a test case too |
Member
Author
I noticed this on main |
kaxil
approved these changes
Oct 14, 2025
Member
kaxil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need a test addition, otherwise lgtm
amoghrajesh
reviewed
Oct 14, 2025
dheerajturaga
force-pushed
the
bugfix/mapped-ti-retry-delay
branch
from
October 15, 2025 22:33
bfca09c to
aa6d79b
Compare
kaxil
reviewed
Oct 15, 2025
kaxil
reviewed
Oct 15, 2025
kaxil
pushed a commit
that referenced
this pull request
Oct 16, 2025
...licit value (#56605)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
(cherry picked from commit 1ab5bb6)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
(cherry picked from commit 1ab5bb6)
snreddygopu
pushed a commit
to Teradata/airflow
that referenced
this pull request
Oct 16, 2025
...licit value (apache#56605)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
abdulrahman305 bot
pushed a commit
to qenex-ai/airflow
that referenced
this pull request
Oct 17, 2025
...licit value (apache#56605)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
abdulrahman305 bot
pushed a commit
to qenex-ai/airflow
that referenced
this pull request
Oct 19, 2025
...licit value (apache#56605)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
TyrellHaywood
pushed a commit
to TyrellHaywood/airflow
that referenced
this pull request
Oct 22, 2025
...licit value (apache#56605)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
When querying the API endpoint for mapped tasks (e.g., /api/v2/dags/{dag_id}/tasks/{task_id}),
the server returned a 500 Internal Server Error if the mapped task didn't have an explicit
retry_delay set. The retry_delay property was using direct dictionary access which raised
a KeyError during serialization.
Changed to use .get() with the default value from SerializedBaseOperator (300 seconds)
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.