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 ,
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.