Validation Activity - Not giving right error

Kothai Ramanathan 941 Microsoft Employee

I have a pipeline which works on files in a folder. At the start of the pipeline is a validate activity to check if files exist. If there are no files, then we do nothing. Because we do not want the pipeline to report an error every time there are no files. As files not being present in a valid business scenario.

However notice that if there are other failures in the validation activity (either the path provided is not right, or the credentials provided are not right), even then it only fails the activity, but not give the error for which it failed.

In the above scenario, I have provided a wrong directory name, and the activity failed, but there is no error that the parameter is wrong. If I do the same thing to a copy activity, it rightly provides an error mentioning that the parameter is wrong.

Because of this, we are not able to identity whether the activity failed because of files not found, or there was real issue when accessing the files. How do we differentiate such cases ?

Kothai Ramanathan 941 Reputation points Microsoft Employee

2021-02-19T09:04:06.253+00:00

To add to the above, if on the failure of the validation activity, I say "@coalesce(activity('Validate if files exist').Error.Message, '')" , it gives an empty string.
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2021-02-19T22:11:53.197+00:00

Hi @Kothai Ramanathan ,

Thanks for bringing this to our notice. Could you please share the error message (inappropriate error) your are receiving?

Thank you

----------

Announcement : Want to participate in Azure Data Factory hackathon'21? Come hack with us :) - https://aka.ms/adfhack21 (Note: Submission Deadline 24th Feb'21)
Kothai Ramanathan 941 Reputation points Microsoft Employee

2021-02-22T04:11:59.973+00:00

@KranthiPakala-MSFT - as shown in the screenshot above, it is not giving any error message. The activity failed, but there is no error message.
KranthiPakala-MSFT 46,422 Reputation points Microsoft Employee

2021-02-23T09:19:28.37+00:00

Thanks @Kothai Ramanathan , for confirming. This seems to be bug but to double confirm, I am reaching out to product team on this issue and will get back to you as soon as I have update from the team.

Thank you for your patience.