Forum Discussion
GEN2 dataflow error - We received multiple duplicate continuation tokens from Azure Storage
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.
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.
Hi v-menakakota
Thanks for the suggestion. I will certainly open a pro ticket once the problem becomes more severe.
Can you please tell me the name of the partner organization that you work for? I have always wondered who works on the Q&A in the forums.
>> raising awareness of such issues is incredibly valuable for all users.
The best way to raise awareness is for Microsoft to do so in their "known issues" page. Everything we accomplish here in these forums is just guesswork. Microsoft is in the position to look at their source code, and find the failing component, and describe the reason(s) why this error message would arise. It is unlikely that there is ambiguity in this error itself, or in the RCA for the error. It is very likely that the error could be simulated on demand. Once this happens, the error should be added to the "known issues" page by Microsoft for the benefit of customers.
Are you able to reach out to the Fabric PG team? Can you please propose to them that they should do the needful? I think it would be the onelake team. I have not had any error messages of this nature when using normal Azure storage containers, so it is almost certainly a bug that is introduced by one of the Fabric PG's.
I hesitate to create another SR given that I spend between 100 and 200 hours a year working on cases with Mindtree and I need to be careful about which bugs to invest time in. Ideally Microsoft would do the heavy lifting for this one, or would add it to the "known issues" page if they don't have a fix yet.
Hi dbeavon3 ,
Thank you for your interest! Due to privacy and data protection policies, I'm unable to disclose the name of the organization I’m affiliated with. My main focus is to contribute to the community by sharing accurate information and helpful content.We really apologies for the inconvenience.
Regarding the PG team, unfortunately we don’t have any specific details or direct contact with them at this time.
Hi v-menakakota Seems odd for you to be providing advice in the community without any credentials, or even a company name. Can you at least say "Authorized Microsoft Partner" or something? Most of the information that is shared on the Internet is judged based on the source, and the fact that your signature says "community support" implies you are a reliable source so I can't see why you can't confirm it.
Unfortunately the meaning of "accurate information" is pretty subjective nowadays. It always depends on the source.
(If you were to say you work for Mindtree, then it would help me avoid making a duplicate/redundant contact with the "pro" support. Or, alternately, I might ask that your fellow MT engineers to refer to your advice in the community and they would consider it even more authoritative, given that you both work in the same org. )
Do you have any process for alerting Microsoft about "known issues"? That is always a much higher quality source of information about bugs, than the discussion in this community.I truly appreciate your help, just want to know who I'm working with.
Hi dbeavon3 ,
We really apologies for the inconvenience, As a community support member, we are here to share guidance based on experience and available resources. We’re kindly asked not to disclose organization names or Microsoft Partner status in the forum, in line with Microsoft’s privacy and community guidelines.
we always recommend that users experiencing persistent or potentially platform-related issues log a support ticket through the Microsoft support channel or if they want to Connect with community members, ask questions, and learn more about Fabric to use the Forum.
Thank you for reaching out to us on the Microsoft Fabric Community Forum.