Forum Discussion
Pipelines and pipeline steps return wrong status
Pipelines and pipeline steps are returning wrong status.
Pipeline returns failed even when all pipeline steps are successful.
Copy activities return failed even when in the background they were successful. This results in duplicated data with retry option enabled.
Copy activity error: #2012 Object reference not set to an instance of an object.
All these problems started happening over the weekend and they continue to happen.
I have these problems happen with all three of my clients where we use Fabric.
Is this also happening to someone else?
This needs to fixed ASAP.
Just heared back from the support with an explanation.
This issue apparantly affected several regions including West Europe.
The problem was a backend storage throttling. This throttling led to delays of failed operations, while status indicators were displayed erroneously.
To resolve this they increased the throttling limits and implemented safeguards and monitoring to prevent similar issues in the future.
And I am happy to report that from the 12th November all pipelines have been running fine.
5 Replies
Just heared back from the support with an explanation.
This issue apparantly affected several regions including West Europe.
The problem was a backend storage throttling. This throttling led to delays of failed operations, while status indicators were displayed erroneously.
To resolve this they increased the throttling limits and implemented safeguards and monitoring to prevent similar issues in the future.
And I am happy to report that from the 12th November all pipelines have been running fine.
Hi Tymok,
What region are you in? It looks like ther eis currently degraded service in the Americas: https://support.fabric.microsoft.com/support/
I recommend opening a support ticket.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hello Tymok,
We are following up regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.
Thank you.
