Is there a list of error codes and their meaning

DEDev 20 Reputation points
2024-08-08T11:50:14.06+00:00

Hi,

As part of custom audit logs, we want to capture errors in case something fails. We tried with getting message from failed activity, but they can be very long, especially in case Notebook fails. So we wanted to switch to store error code, and have a cheat sheet, but I can't find online if there is list of error codes. 2 came while testing, 6000 where notebook is note found, and 6002 where there is bug in the code.

E.g.

@activity('NotebookActivity').error.errorCode
Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,902 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,643 questions
{count} votes

Accepted answer
  1. Vinodh247 19,656 Reputation points
    2024-08-08T12:45:40.5466667+00:00

    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.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.