Forum Discussion

JP_Wisco's avatar
JP_Wisco
Icon for Helper I rankHelper I
2 years ago
Solved

Pipeline fails to start: "internalServerError executing request"

Edits: Accidentally edited the wrong post, then undid the edit, then edited to add edits note.   I don't have a lot of experience with pipelines but didn't find this issue on a skim of the troubles...
Need Help
  • v-cboorla-msft's avatar
    v-cboorla-msft
    2 years ago

    Hi JP_Wisco 

     

    Apologies for the delay in response from my end.

    Following up to see whether the issue got resolved or still you are facing the issue?

    The error "Internal Server Error - Executing requests." could be a transient network issue.

    If the issue still persists. Please reach out to our support team so they can do a more thorough investigation on why this it is happening. It's difficult to tell what could be the reason for this performance. If its a bug, we will definitely would like to know and properly address it.

    Please go ahead and raise a support ticket to reach our support team:

    https://support.fabric.microsoft.com/support

     

    After creating a Support ticket please provide the ticket number as it would help us to track for more information.

     

    Thank you.

nielsvdc's avatar
nielsvdc
Icon for Super User rankSuper User
1 year ago

For those seeking for an answer to this error message "InternalServerError executing request". For us the problem was that we were using the Teams activity to send a message to a channel, but the activity needed re-authenication for the pipeline to run.

If you get this error, please check if any of your pipeline activities have broken links to other Fabric items, like other pipelines or notebook, or activities need the be re-authenticated. This might me caused by deploying the pipeline using DevOps or Git to another workspace when using DTAP branches.