Azure Data Factory - Internal Server Error

Question

Azure Data Factory - Internal Server Error

Mickael GERVAIS (Externe) 5

Hi,

I'm using Azure Data Factory.

I'm unable to run pipeline since yesterday.

I've the following error:

{ "code": "InternalServerError", "message": null, "target": "pipeline//runid/79772434-35c1-4633-9b78-8e92bef33e48", "details": null, "error": null }

I didn't change anything on the DataFactory, and the pipeline is published.

I've checked the Health Status and there is no problem.

Regards

Chandra Boorla 12,285 Reputation points Microsoft External Staff Moderator

2025-05-07T16:59:32.8333333+00:00
@Mickael GERVAIS (Externe)

The "InternalServerError" you are experiencing in Azure Data Factory is a generic 500-level error, which typically indicates an issue on the service side rather than something you directly configured. Since the error message and details are null.

Here are a few steps you can take to troubleshoot:

Implement Retry Logic - Since transient issues can sometimes cause internal errors, consider adding a retry policy to your activities. This can help automatically recover from temporary glitches.

Review the Pipeline Run Details - Go to the "Monitor" section of your Azure Data Factory.

Locate the run ID: 79772434-35c1-4633-9b78-8e92bef33e48.

Check the activity logs for any specific error messages.

Review Compute Settings - Ensure that the compute size/type for any Data Flow activities is appropriate for the data being processed. If the data size has increased or if you have many complex transformations, a larger compute may be needed.

Verify Dataset Connections - Double-check that all linked service connections (source and sink) are working correctly. Test each connection in the pipeline settings to ensure they are accessible.

Adjust Parallel Activities - If you are using "ForEach" or other parallel activities, try reducing the number of concurrent executions. Resource contention can cause internal server errors when too many activities run at once.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.
Chandra Boorla 12,285 Reputation points Microsoft External Staff Moderator

2025-05-08T16:47:26.58+00:00

@Mickael GERVAIS (Externe)

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Morgan S 0 Reputation points

2025-05-09T08:18:22.99+00:00

Hello,

We are experiencing a similar issue here.
Everything were working nice, and since wednesday morning we can't debug a pipeline.

When we run the debug, in monitor view a different pipeline is called.
We found out that, if we rename all pipelines called in the monitor view, the pipeline we wanted to invoke worked.
However, we can't go back to their old names as the Internal Server keep happening after going back.

If any of you have any clue of what is happening, don't hesitate to share information !

Thank you in advance !

Your answer

Chandra Boorla 12,285 Reputation points Microsoft External Staff Moderator

2025-05-07T16:59:32.8333333+00:00

@Mickael GERVAIS (Externe)

The "InternalServerError" you are experiencing in Azure Data Factory is a generic 500-level error, which typically indicates an issue on the service side rather than something you directly configured. Since the error message and details are null.

Here are a few steps you can take to troubleshoot:

Implement Retry Logic - Since transient issues can sometimes cause internal errors, consider adding a retry policy to your activities. This can help automatically recover from temporary glitches.

Review the Pipeline Run Details - Go to the "Monitor" section of your Azure Data Factory.

Locate the run ID: 79772434-35c1-4633-9b78-8e92bef33e48.

Check the activity logs for any specific error messages.

Review Compute Settings - Ensure that the compute size/type for any Data Flow activities is appropriate for the data being processed. If the data size has increased or if you have many complex transformations, a larger compute may be needed.

Verify Dataset Connections - Double-check that all linked service connections (source and sink) are working correctly. Test each connection in the pipeline settings to ensure they are accessible.

Adjust Parallel Activities - If you are using "ForEach" or other parallel activities, try reducing the number of concurrent executions. Resource contention can cause internal server errors when too many activities run at once.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.
Chandra Boorla 12,285 Reputation points Microsoft External Staff Moderator

2025-05-08T16:47:26.58+00:00

@Mickael GERVAIS (Externe)

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Morgan S 0 Reputation points

2025-05-09T08:18:22.99+00:00

Hello,

We are experiencing a similar issue here.
Everything were working nice, and since wednesday morning we can't debug a pipeline.

When we run the debug, in monitor view a different pipeline is called.
We found out that, if we rename all pipelines called in the monitor view, the pipeline we wanted to invoke worked.
However, we can't go back to their old names as the Internal Server keep happening after going back.

If any of you have any clue of what is happening, don't hesitate to share information !

Thank you in advance !

Share via

Azure Data Factory - Internal Server Error

Your answer