Skip to content

Signal argument deserialization errors not using workflow-specific logger or giving enough context #1322

@cretz

Description

@cretz

Describe the solution you'd like

Unlike other arg deserialization errors in a workflow which fail the task by default, signal deserialization errors are treated special to log-and-ignore to not fail the entire workflow. However, the log is not using the workflow logger at

logger.exception(
f"Failed deserializing signal input for {job.signal_name}, dropping the signal"
)
meaning there is not enough context to diagnose.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions