Hi DEDev,
Thanks for reaching out to Microsoft Q&A.
There is no comprehensive, official list of error codes and their meanings for ADF available online. The error codes you mentioned (2, 6000, and 6002) are not standard ADF error codes. When an activity fails in ADF, you can access the error message and other details using the @activity('activityName').error expression. However, as you noted, these error messages can be lengthy, especially for failures in notebook activities. To capture more concise error information, you can use the @activity('activityName').error.errorCode expression to retrieve a numeric error code. However, these error codes are specific to the type of activity and the failure scenario. They are not part of a standardized error code system.
For example, if a Notebook activity fails due to a syntax error in the notebook code, the error code might be something like "6002" as you mentioned. But this code is not predefined by ADF and its meaning is specific to the notebook failure scenario. When troubleshooting ADF pipeline failures, it's still recommended to check the full error message, which may provide more context and details about the failure, even if the message is lengthy.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.