pipelines

883 Topics

Copy Data Activity failed on Upsert
Hi I'm currently building a pipeline to copy data from a Fabric warehouse to a Fabric lakehouse. Everything from source to destination is configured in a config table. Including the column mapping. While executing the pipeline with Table action: "Overwrite" defined, the pipeline executes succesfully. When changing the Table action to "Upsert", the pipeline fails. Which Error do I get? ErrorCode=FailedToUpsertDataIntoDeltaTable,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Hit an error when upsert data to table in Lakehouse. Error message: Specified cast is not valid.,Source=Microsoft.DataTransfer.Connectors.LakehouseTableConnector,''Type=System.InvalidCastException,Message=Specified cast is not valid.,Source=Microsoft.DataTransfer.Connectors.LakehouseTableConnector,' What did I configure? How does the input for the Key columns look like during execution? Does anyone has any ideas? I have been searching for this specific error but couldn't find any details... Thanks for the help :)
olivs
22 hours ago Place Pipelines
Views
0likes
Comments
Workspace Identity works in one workspace but fails in another when executing Notebook Activity
Hi everyone, I'm troubleshooting an issue with Notebook Activity + Workspace Identity (WI) in Microsoft Fabric Data Factory and would like to know if anyone has experienced something similar. Scenario I'm trying to execute a notebook from a pipeline using a Workspace Identity connection. The notebook itself is very simple and does not require: Lakehouse Environment External connections The execution fails before Spark starts. Notebook Error An unexpected error encountered while preparing spark operation execution. The user access token was not found. The user session may have expired or the user is no longer valid. Please sign in again. Additional observations: In the notebook run history, the "Submitted By" column appears as "--" The notebook never reaches Spark execution Pipeline Error Notebook execution failed at Notebook service with http status code - '200' Failed to create session for executing notebook. Notebook execution is in Failed state. What I have already validated ✅ Workspace Identity exists and is active in Entra ID ✅ Workspace Identity is included in the Security Group allowed to use Fabric APIs ✅ Tenant setting "Service principals can call Fabric public APIs" is enabled ✅ Workspace Identity is Workspace Admin ✅ Workspace Identity is successfully used to access Azure Data Lake Storage Gen2 ✅ Notebook Activity is configured to use a Workspace Identity connection ✅ Notebook owner account is active and valid ✅ Pipeline owner account is active and valid ✅ No Environment attached ✅ No Lakehouse attached ✅ No external connections inside the notebook ✅ Created a brand-new notebook containing only: print("hello") ✅ Created a brand-new pipeline containing only a Notebook Activity Same result. ✅ The same Notebook Connection with Workspace Identity works successfully in another workspace Comparison with another workspace I have another workspace with: The same tenant Different Fabric capacity The same geography Different Security Group The same Fabric API tenant settings The same Notebook Connection owner and the exact same configuration works correctly there. Additionally: The same Notebook Connection was tested in both workspaces The same Workspace Identity pattern is used The working workspace can access Key Vault and execute notebooks through pipelines without issues The only variable that seems to change is the workspace itself. Additional Observation The Workspace Identity appears to be functioning correctly because it is already being used successfully to authenticate against Azure resources such as ADLS Gen2. Because of this, the issue does not appear to be related to Entra permissions, Fabric API permissions, or Workspace Identity access to Azure resources. Instead, it seems related to one of the following: Notebook Activity + Workspace Identity integration Session creation Workspace metadata Workspace-specific configuration Question Has anyone encountered a situation where: Workspace Identity authentication works for ADLS and Key Vault The same Notebook Connection works in another workspace Notebook Activity only fails in one specific workspace The error is related to: "The user access token was not found" "Failed to create session for executing notebook" Empty "Submitted By" field I'm trying to determine whether this is: A workspace-specific metadata issue A Notebook Activity bug A Workspace Identity provisioning issue An undocumented prerequisite for Workspace Identity execution Any insights would be greatly appreciated. Thanks!
Solved
santiago-marano
1 day ago Place Pipelines
Views
0likes
Comments
Intermittent Gateway Connectivity Error in Fabric Pipelines
Hi everyone, I'm posting because we're experiencing an issue with some of our Fabric pipeline executions and would like to know if anyone has encountered something similar. We have an on-premises SQL Server and an on-premises data gateway installed on a dedicated gateway server. The issue is that, intermittently, approximately 60% of pipeline executions fail when a pipeline activity executes a query against the SQL Server database. The error returned is: "Please check your network connectivity to ensure your on-premises data gateway can access ne.frontend.clouddatahub.net and restart the service to retry the connection again once the connectivity issue has been resolved." What makes this error difficult to understand is that: We currently have more than 800 Power BI Dataflows Gen1 running through the same gateway, and none of them experience this issue. The same pipeline sometimes runs successfully and sometimes fails with the error above. Because of this inconsistent behavior, it does not appear to be a permanent connectivity problem between the gateway and the cloud service. Has anyone experienced a similar issue or found a solution? Any guidance or suggestions would be greatly appreciated. Thanks in advance!
Solved
Aventuran
9 days ago Place Pipelines
Views
0likes
Comments
How can AI agents improve Microsoft Fabric Data Factory pipeline automation?
I am exploring how AI agents can help make data pipeline development and monitoring more efficient in Microsoft Fabric Data Factory. Some potential use cases: Automatically creating pipeline workflows based on business requirements Detecting pipeline failures and suggesting fixes Optimizing data movement and transformation steps Monitoring data quality and identifying anomalies Triggering automated actions through APIs or external tools I would like to understand how teams are currently combining AI agents with Fabric Data Factory. Are you using: AI-assisted pipeline generation? Automated error analysis and recovery workflows? Fabric notebooks with AI models for data operations? Custom agents connected with Data Factory pipelines? Would appreciate insights, real-world examples, or architecture patterns from developers working with Fabric Data Factory automation.
Solved
codeautomation
9 days ago Place Pipelines
Views
0likes
Comments
Bug: QuickBooks connector (QuickBooks for Pipeline) fails OAuth login
When attempting to create a connection of type QuickBooks for Pipeline (Cloud category) via Manage Connections and Gateways in Microsoft Fabric, with the authentication method automatically set to OAuth 2.0, clicking the Edit credentials button results in an error when trying to initiate the OAuth login flow. Error message: Unable to start OAuth login for this data source. Connection string is not supported. Details: Query contains unsupported function. Function name: QuickBooksForPipeline.Contents Session Id: 6fb86dae-dc71-4a06-8f7f-b99aee7885df RequestId: 710bfcb8-ff7a-444d-90dc-c2dcc311e0f9 Cluster URI: https://api.powerbi.com Status code: 400 Time: Fri Sep 11 2026 07:54:51 GMT+0300 (Eastern European Summer Time) Steps to reproduce: In a Fabric workspace, open a Copy Data activity (Source) or go to Manage Connections and Gateways. Click "+ New" to create a new connection. Select connection type Cloud. Search for and select QuickBooks for Pipeline as the data source. Authentication method is automatically set to OAuth 2.0. Click Edit credentials. The error above appears instead of the expected QuickBooks OAuth consent screen. Expected behavior: Clicking Edit credentials should open the standard Intuit OAuth 2.0 consent screen, as described in the QuickBooks connector documentation for Data Factory / Fabric pipelines. Impact: It is currently impossible to create a working QuickBooks Online connection in a Fabric pipeline using this connector, which blocks migrating an existing pipeline (where tokens are currently passed manually as parameters) to native OAuth authentication. Environment: Microsoft Fabric (trial capacity), browser: Chrome, date: 2026-09-11.
Vitaliy3
9 days ago Place Pipelines
Views
0likes
Comments
Fabric Data Factory system variable pipeline().triggertype
Hello I would be grateful if someone from Microsoft would clarify whether, for Fabric Pipelines, the system variable pipeline.triggertype() is officially supported. Our pipeline is set up to be triggered by a schedule. At the moment, on pipeline run, when we pass the value of the system variable pipeline.triggertype() through to our own logging tables, it returns the value of either Manual or 1. This is different to what is stated in the pipeline development user interface, which shows that it passes through value of either Manual or Scheduler. Also in the documentation below re pipeline scope variables for Fabric data factory, no mention is made of the system variable pipeline.TriggerType() https://learn.microsoft.com/en-us/fabric/data-factory/expression-language#pipeline-scope-variables Please clarify if the values of Manual and 1 currently being passed through are a reliable means to determine whether the pipeline was a manual or scheduled trigger - or will these values be subject to change? If not reliable, I will have to develop a manual work around. Many thanks for your help in anticipation.
Solved
JaneLHunt
19 days ago Place Pipelines
Views
0likes
Comments
Faulting application FabricPipelineWorker.exe
Hello, we installed an On-premise data gateway version 3000.330.1 (August 2026) on a Windows Server 2025. Every time we connect to SAP over SAP Table Application Server to our SAP System on SAP Cloud, we get the following error: Application: FabricPipelineWorker.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message) at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MultiplexingMessenger.OnMessageToOtherChannel(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, MessageToOtherChannel) at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message) at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__1`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.DataTransfer.Common.ProcessManagement.RemoteService.RemoteServiceEnvironment+<DisposeServiceStubsAsync>d__4.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.WorkerContainer+<StartAsync>d__11.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program+<Main>d__1.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program.<Main>(System.String[]) AND: Faulting application name: FabricPipelineWorker.exe, version: 5.68.9706.2, time stamp: 0x900a871d Faulting module name: KERNELBASE.dll, version: 10.0.26100.33158, time stamp: 0x4332201f Exception code: 0xe0434352 Fault offset: 0x00000000000c75fa Faulting process id: 0x2234 Faulting application start time: 0x1DD3B1901C52B57 Faulting application path: C:\Program Files\On-premises data gateway\FabricIntegrationRuntime\5.0\Shared\FabricPipelineWorker.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: a3bc643f-227b-4f9e-b7b7-45ff005eb05f Faulting package full name: Faulting package-relative application ID: Has anyone an idea? BR Thomas
ThomasPluemper
26 days ago Place Pipelines
Views
1like
Comments
Fabric Pipeline stuck on Loading - pipeline editor does not open
Hi, I am facing an issue with Microsoft Fabric Data Pipelines. The pipeline editor remains stuck on Loading and the activities/canvas never appear. The issue happens in multiple workspaces in the same tenant. I also created a new pipeline in another Fabric trial workspace, but it has the same issue. Lakehouse is working normally, but Pipeline remains stuck on Loading. I have tried refreshing and reopening Fabric and testing in another workspace, but the issue persists. Is anyone else experiencing this issue? Could this be a Fabric service-side issue? I have attached screenshots showing the Loading screen. Thanks
Solved
NaraayaPC
1 month ago Place Pipelines
Views
1like
Comments
Fabric Pipeline Lakehouse sink fails across multiple workspaces with invalid quoted UTF-8 charset
We are unable to use Microsoft Fabric Pipelines to copy data from an on-premises SQL Server into either the Tables or Files area of a Fabric Lakehouse. The SQL Server source is reached successfully, authentication succeeds, the query executes, and the Pipeline reads and copies the returned rows. However, the Lakehouse sink fails before writing any data or creating a file. The consistent error is: ErrorCode=LakehouseOperationFailed The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. '"utf-8"' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method. Parameter name: name The quoted encoding value "utf-8" does not appear anywhere in the Pipeline JSON configuration. The exception appears to be raised when the Microsoft Data Transfer client processes a response during the Lakehouse write operation. Reproduction steps Create a new Fabric workspace assigned to the F2 capacity. Create a new Lakehouse in that workspace. Create a Fabric Data Factory Pipeline. Add a Copy Data activity. Use the existing SQL Server Database connection through the on-premises gateway. Use SELECT 1 AS TestID as the source query. Configure the destination as Bronze_LH_1/Files/Test1/TestID. Run the Pipeline. The source row is read successfully, but the Lakehouse sink fails before writing the file. Full Pipeline Error Code: 27370 ErrorCode=LakehouseOperationFailed, Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException, Message=Lakehouse operation failed for: The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. Source=Microsoft.DataTransfer.ClientLibrary, Type=System.InvalidOperationException, Message=The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. Source=mscorlib, Type=System.ArgumentException, Message='"utf-8"' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method. Parameter name: name Source=mscorlib Troubleshooting Already Completed The following tests have already been performed: Confirmed Microsoft Fabric is enabled in tenant settings. Confirmed users can create Fabric items. Confirmed the workspace is assigned to an active Fabric F2 capacity. Confirmed the capacity is in the correct region Confirmed the SQL Server Database connection is Online and Ready. Confirmed the on-premises data gateway shows no warnings. Confirmed Windows authentication credentials are valid. Successfully executed and read results from SELECT 1 AS TestID. Confirmed the Pipeline read and copied one row from SQL Server. Tested a source view named [DataWarehouse].[BI_vw].[AccountTypeNames]. Reduced the source query to the literal query SELECT 1 AS TestID. Tested a Lakehouse Table destination. Tested a Lakehouse Files destination. Tested the default dbo destination schema. Tested a custom BI_vw destination schema. Tested the Copy Job assistant. Tested a manually configured Pipeline Copy Data activity. Created new Lakehouses and repeated the test. Created an entirely new Fabric workspace and repeated the test. Reproduced the identical error in both the original and new workspaces. Successfully uploaded a file manually through the Lakehouse browser interface. Confirmed manual OneLake/Lakehouse file access works. Confirmed no Pipeline JSON property specifies charset="utf-8". Findings The testing indicates: On-premises gateway connectivity: Successful Windows authentication: Successful SQL Server query execution: Successful Source data read: Successful Row transfer from source: Successful Manual Lakehouse file upload: Successful Pipeline Lakehouse sink write: Failed The issue is reproducible across multiple workspaces, Lakehouses, destination types, and source queries. The original workspace’s history as a Power BI workspace was eliminated as a cause by reproducing the issue in a newly created Fabric workspace.
Solved
ShayneY75
1 month ago Place Pipelines
Views
0likes
Comments
A bug in the Data pipeline expression builder
Since last week's Fabric update, the Expression Builder is generating incorrect expressions when selecting pipeline parameters. For example, instead of generating: It writes @linkedService().<parameter_name> instead of @pipeline.parameters.<parameter_name>. The expression is immediately flagged with an "UnsupportedConcept" error. Additionally, the value cannot be saved even after manually correcting the expression to the proper pipeline parameter syntax. The issue occurs with both newly created and existing parameters, suggesting a regression introduced in the latest Fabric update.
Solved
tarektm17
1 month ago Place Pipelines
Views
0likes
Comments