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 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.Hi v-menakakota
Earlier you said it "was not a commonly reported issue". Is this based on a guess, or based on the number of posts in the forum, or based on your visibility into support cases?Has this bug ever been reported via support ticket (pro support at CSS)?
I'm trying to determine when to report the issue to Mindtree/Microsoft, and whether it might be better to let others spend time on those tickets since I have plenty of other bugs to deal with.
Again, it would be helpful for you to introduce yourself in some way so we can determine what you mean when you claim a problem is not commonly reported. Assuming you are NOT working for either Microsoft or Mindtree, then you probably don't have any awareness of how common a bug might be. That information is extremely valuable and most of us don't have a way of knowing one way or another. I find that even the most common types of problems will not be added to the "known issues" list.
Hi dbeavon3 ,
Thank you again for your thoughtful feedback it's clear you're deeply committed to improving the platform experience, and that’s genuinely appreciated.
When I mentioned this doesn’t seem to be a commonly reported issue, I was referring to what’s visible in the public community space. I don’t have access to internal support data, so my comments are based on community insights only.
For issues like this,if you have Pro license raising a Pro Support ticket is still the most effective way to ensure it gets in front of the right engineering teams. I completely understand the time commitment, but it really helps drive visibility and resolution at the right level.
Thanks again for being an engaged and proactive voice in the community.