Thanks for reaching out to Informatica Community Discussion.
You can introduce a throw step in taskflow design.
When you add a Throw step to the error-handling path, the error handling path breaks off from the main path of the taskflow. If a fault occurs, the taskflow takes the path that you define for handling the error. For example, in the error path, you might add a Notification Task step to send an email notification followed by a Throw step to catch the fault and stop the taskflow execution.
Please follow the below hyperlink for more details on the Throw step.
Also, feel free to reach out in case of further queries\concerns.
Thanks for response.
We already applied the Throw exception at Parent taskflow and subtaskflow level. The issue is - when my subtaskflow suspended, still parent taskflow doesn't fail but keeps on showing in running status. Please refer last screenshot in my original post.
Nature of Taskflow is, it goes into Suspended state whenever there is a failure. If this taskflow is used as sub-Taskflow then the Parent taskflow will be in running status till Sub-Taskflow is made into Success/Failure. So you will have to build custom error handling using using Throw Step as suggested by Varun.
Is throw step not helping in stopping the execution of the taskflow, and set the taskflow status to failed?
Let us know if any queries.
You have to use the fault handling event to mark it for failure:
Please keep us posted if this article helped.