Forum Discussion
Pipeline fails to start: "internalServerError executing request"
- 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.
After copying a pipeline, I encountered this fail as well.
The issue got resolved by signing in to my Office 365 Outlook account in one of the Outlook 365 activities of our pipeline and allowing access. 🙂
- igork2 years agoRegular Visitor
Thank you, that helped me 🙂
- TAPeri1 year agoFrequent Visitor
I got the same issue! After copying a pipeline with an "Office 365 Outlook" activity, I started getting the "Internal Server Error" message. After sign in again in one of the pipelines, the following warning showed up on the other pipeline
"Last modified by 'undefined'. Since the activity was modified by another user, please sign in with your account to modify the activity."
I had to rename one of the activities and sign in once again, and it has worked fine since then.