Forum Discussion
GEN2 dataflow error - We received multiple duplicate continuation tokens from Azure Storage
Can someone tell me what this means?
MashupException.Error: Failed to insert a table., InnerException: We received multiple duplicate continuation tokens from Azure Storage.
We have a pretty simple GEN2 dataflow and it suddenly failed today with a meaningless error. I would like to understand what it means, and why it happens. I'm guessing it is some sort of regression since I've never seen this before and it seems like the type of thing that we would have encountered by now.
I think this is correlated to a release train that has been sent to our regions this weekend.
Any help would be appreciated. I have way too many tickets with Mindtree right now and this one is probably going to take two or three weeks of engagement. They never put their bugs in their "known issues" pages, so I thought I would at least share this here.
I spoke with a Mindtree engineer. The release train went to production on 4/5 and this unusual error appeared to us for the first time in our daily GEN2 refresh on 4/7.
They want me to open a new ticket (SR). After that Mindtree promised to send the bug to Microsoft via ICM. They claim there are no prior ICM's with a similar error message yet:
We received multiple duplicate continuation tokens from Azure Storage.
I will probably send this issue thru pro support (Mindtree) once our users start to notice/complain. It may be a few days for them to realize their stuff is broken (again). The worst part is that this new problem came up in the same "train" that deployed a fix for a different problem. A very LARGE part of my job these days involves talking to Mindtree support about Fabric bugs. Some days I find it very troublesome to be a Fabric customer.
13 Replies
I spoke with a Mindtree engineer. The release train went to production on 4/5 and this unusual error appeared to us for the first time in our daily GEN2 refresh on 4/7.
They want me to open a new ticket (SR). After that Mindtree promised to send the bug to Microsoft via ICM. They claim there are no prior ICM's with a similar error message yet:
We received multiple duplicate continuation tokens from Azure Storage.
I will probably send this issue thru pro support (Mindtree) once our users start to notice/complain. It may be a few days for them to realize their stuff is broken (again). The worst part is that this new problem came up in the same "train" that deployed a fix for a different problem. A very LARGE part of my job these days involves talking to Mindtree support about Fabric bugs. Some days I find it very troublesome to be a Fabric customer.
This happened to my dataflow gen 2 as well. I am getting this error randomly from any query inside the DF. I have contacted Mindtree engineer but unfortunately we couldn't come up with a solution so far. And the weird thing is they can't see any error code from their side so far.
Hi dbeavon3 ,
Thank you for bringing this to our attention and for providing detailed context around the issue. We understand how disruptive it can be to encounter unexpected errors, particularly in workflows that have been running reliably.
The error message "We received multiple duplicate continuation tokens from Azure Storage" typically indicates a low-level issue related to data pagination when retrieving content from Azure Data Lake Storage Gen2. While this is not a commonly reported issue, the timing you've identified with the recent release may point to a potential regression.
At this stage, we recommend raising a support request (SR) through your Pro Support channel. This will ensure the appropriate teams can investigate further and take necessary action.
We appreciate you sharing this with the community — raising awareness of such issues is incredibly valuable for all users.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
We had the same error on 2 of our dataflows this morning after switching capacities, republishing fixed the issue for us.
