Skip to content

Append some details to error messages #676

@cretz

Description

@cretz

Describe the solution you'd like

For activity failure, application failure, child workflow failure, Nexus handler failure, Nexus operation failure, and timeout failure, we should append all non-"details" properties to the message. Java already does this for most, Go for some, other languages do not at all.

May need to discuss if this is something we want to do with application failure since it is user created. Java and Go do though.

Per-SDK Tickets

  • Go - Already done for some fields/errors
  • Java - Done for all but Nexus handler exception
  • Core - N/A
  • TypeScript - TODO
  • Python - TODO
  • .NET - TODO
  • Ruby - TODO
  • PHP - TODO
  • Temporal CLI - N/A

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