Capture error message/failure reason on task level

[sonamdolphin9192]

Hi,
I want to capture error message/failure reason on task level in argo workflow.
I have checked here https://argo-workflows.readthedocs.io/en/latest/variables/ but nothing has been specify for error message on task level.
Here is the case-

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: exit-handler-with-param-
  labels:
    workflows.argoproj.io/test: "true"
  annotations:
    workflows.argoproj.io/description: |
      onExitTemplate enables workflow to pass the arguments (parameters/Artifacts) to exit handler template.
    workflows.argoproj.io/version: ">= 3.1.0"
spec:
  entrypoint: main
  templates:
    - name: main
      dag:
        tasks:
          - name: task-1
            template: output
            hooks:
              exit:
                template: exit
                arguments:
                  parameters:
                    - name: error_message
                      value: "{{tasks.task-1.error_message}}" # Need error message on task level
    
    - name: output
      container:
        image: python:alpine3.6
        command: [sh, -c]
        args: ["echo -n hello world > /tmp/hello_world.txt"]
      outputs:
        parameters:
          - name: result
            valueFrom:
              default: "Foobar"  
              path: /tmp/hello_world.txt
    
    - name: exit
      inputs:
        parameters:
          - name: error_message
      script:
        image: python:alpine3.6
        command: [ python ]
        source: |
          print("{{inputs.parameters.error_message}}")

[jswxstw]

There is a variable workflow.failures in exit handler.

[sonamdolphin9192]

Yes there is. But I want to capture on tasks/steps level

[jswxstw]

It is not supported yet, there are only variable workflow.failures and lastRetry.message has the node error message.
You may need to extract task/step level message from workflow.failures now.

[sonamdolphin9192]

Can we log a ticket as a feature request for this ?

[jswxstw]

I think this feature will not be accepted because task/step level messages usually only contain exitCode like "Error (exit code 1)", which tasks.<TASKNAME>.exitCode and steps.<STEPNAME>.exitCode can be used instead.
If you want to expose meaningful error info, you need to save it into /dev/termination-log, which you can also save it to outputs.