What causes Fabric Pipeline Error 3608?

The Azure Function returned a non-2xx HTTP status code such as 401 (unauthorized), 404 (not found), or 500 (internal server error). The function key or URL provided in the activity definition is incorrect or has expired. The Azure Function App is stopped, restarting, or experiencing an outage. The function code itself threw an unhandled exception and returned an error response

How do I fix Fabric Pipeline Error 3608?

Step 1: Note the specific `%statusCode%` and `%message%` values from the error output in the pipeline run details.. Step 2: If the status code is 401 or 403, verify that the function key in the activity definition is valid and has not been rotated or revoked.. Step 3: If the status code is 404, confirm the function name and Function App URL are correct and that the function is deployed and published.. Step 4: If the status code is 500, check the Azure Function App's Application Insights or log stream for runtime exceptions thrown by the function code.. Step 5: Test the function endpoint directly using a tool like Postman or curl with the same key and payload to isolate whether the issue is in the pipeline or the function.

High severityconnectivityMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 3608

What does this error mean?

The Fabric pipeline successfully attempted to call the specified Azure Function, but the invocation failed with an HTTP error status code and an error message returned by the function. This indicates an issue with the function itself or its configuration rather than the pipeline definition.

Common causes

1The Azure Function returned a non-2xx HTTP status code such as 401 (unauthorized), 404 (not found), or 500 (internal server error)
2The function key or URL provided in the activity definition is incorrect or has expired
3The Azure Function App is stopped, restarting, or experiencing an outage
4The function code itself threw an unhandled exception and returned an error response

How to fix it

1Step 1: Note the specific `%statusCode%` and `%message%` values from the error output in the pipeline run details.
2Step 2: If the status code is 401 or 403, verify that the function key in the activity definition is valid and has not been rotated or revoked.
3Step 3: If the status code is 404, confirm the function name and Function App URL are correct and that the function is deployed and published.
4Step 4: If the status code is 500, check the Azure Function App's Application Insights or log stream for runtime exceptions thrown by the function code.
5Step 5: Test the function endpoint directly using a tool like Postman or curl with the same key and payload to isolate whether the issue is in the pipeline or the function.

Frequently asked questions

How do I find the actual error message from the Azure Function in the pipeline run output?

In the Fabric pipeline monitoring view, click on the failed Azure Function activity run and expand the Output tab. The `%statusCode%` and `%message%` placeholders will be populated with the actual values returned by the function.

Will retrying the pipeline fix Error 3608?

Only if the cause is transient, such as a cold start timeout or momentary Function App unavailability. If the root cause is a bad function key, incorrect URL, or a bug in the function code, retrying will not help without first fixing the underlying issue.