Hi Zeeshan Saleem,
From the description of the issue it looks like the workflow stopped at one point on time ( before reaching the email task ) but even afterwards you did not receive an email notification.
I am not sure at what point the workflow stopped and was the workflow properly recovered.
Maybe attaching the workflow & DIS logs here would give some clue?
You can also attach here the screenshot of how the workflow looks and where is the notification task placed.
Apart from this, you can refer to the following KB article which talks about how to send notification upon failure of a job ( mapping task in workflow ). This is not related to workflow recovery but have a look in case you are looking for it:
Can you please share the workflow run logs and the DIS logs?
The error message that I see in the logs attached here are not related to recovery.
For some reason the mapping task is failing. The error message says that there is a mismatch between the number of ports defined in the mapping and the number of columns actually being fetched. ( I cannot say exactly where ).
You said that the same mapping was working fine before. It might be possible that sources / targets are corrupt. Can you try re-creating them & see if the error persists?
Thanks for your response. As I explain earlier, we are able to send email in case of successful execution but unable to send if job fails.
So we intentionally did modifications in job for failure and to test the failure condition.
In above scenario job is failed and as per condition, email notification must trigger but due to recovery option, workflow stopped on failure point.
Please review the complete scenario and confirm if we need to configure anything else in order to achieve this functionality.
From the workflow log I see that the mappingtask has failed due to some source issue and it is in suspended state. In case if you are looking for the mappingtask to skip and proceed further with the flow and trigger the notification, then you need to select Mappingtask -> recovery strategy -> Skip task instead of restart task.
If you have enabled recovery, then we need to ensure that the mappingtask issue is fixed and then recover the workflow.
For more information you can refer the Developer Workflow Guide -> Workflow Recovery.
Hope this helps.
Adding to Muzamil's reply here: What he said is right in case you want to send out the email when workflow recovery is being performed. If you don't skip the task, it would be like being stuck in an infinite loop of mapping task failure and never being able to exit and move forward to notification task.
In case you want to send out the email notification as soon as task fails, perhaps we can check the workflow design logic ( you can attach the export of the workflow here along with the Informatica product version ).