Forum Discussion
RunTimeTransferContext Error in Fabric Pipeline When Copying Data from Lakehouse to Warehouse
- Anonymous1 year ago
Hi RoopanshGupta
Thank you for reaching out microsoft fabric community forum.
This is an intermittent issue, and we have not been able to identify the root cause so far. If the issue persists in the future, we recommend raising a high-priority support ticket for immediate assistance.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If this solution helps, please consider giving us Kudos and accepting it as the solution so it can assist other community members.
Thank you.
Experiencing the same issue, it suddenly began on 2025-05-19 despite no changes, It has worked for atleast 3 months prior to this without any issues.
Our Data pipeline does similar things to yours, collecting data from Lakehouse / Warehouse endpoints and copying data into an external Azure SQL database.
We're using TabularTranslator to dynamically work with JSON definitions of our tables /columns / keys in both source and sink.
We then iterate a list of tables with different sources (2 lakehouses, 1 warehouse) that all get upserted into the same target destination (Azure SQL).
Suddenly we're getting the exact same error message as you've posted.
ErrorCode=UserErrorInvalidValueInPayload,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to convert the value in 'transferContext' property to 'Microsoft.DataTransfer.Runtime.TransferContext' type. Please make sure the payload structure and value are correct.,Source=Microsoft.DataTransfer.DataContracts,''Type=System.InvalidCastException,Message=Object must implement IConvertible.,Source=mscorlib,'I have also verified that data types of source tables have not changed.
However, in our cases, the entire flow still works for our warehouse source tables, It's just our lakehouse tables, from both lakehouses, that get this error.
We're still able to extract and upsert data from all warehouse tables.
This really feels like backend changes in the platform, or transient errors.
I haven't raised any support with Microsoft over this yet (Got 3 other ongoing tickets that are exhausting me).
There is no official Service Status issue registered in the Admin Portal ServiceHealth either.