Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

terminateReason in TERMINATE task only accepts string values. #3048

@dougsillars

Description

@dougsillars

Describe the bug
In the TERMINATE task, the terminateReason input parameter only accepts a string. For example:

"terminateReason" :"Oh No! the workflow terminated!"

However, if you attempt to pass in a variable:

"terminateReason" :"${get_error_message.output.result}"

The failure workflow does not receiev the variable value - it receives the string "${get_error_message.output.result}"

Details
Conductor version:
Latest OS build
Persistence implementation: Cassandra, Postgres, MySQL, Dynomite etc
Queue implementation: Postgres, MySQL, Dynoqueues etc
Lock: Redis or Zookeeper?
Workflow definition:

Task definition:

"name": "terminate_fail_error",
"taskReferenceName": "address_error",
"inputParameters": {
"terminationStatus": "FAILED",
"terminationReason": "${get_error_message.output.result}",
"workflowOutput": {
"error_message": "${get_error_message.output}"
}
},
"type": "TERMINATE"
}

workflow JSON has the following entry:

"reasonForIncompletion":"${get_error_message.output.result}"

Expected - the value of the variable:

"reasonForIncompletion":"Address not found."

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions