Dataflows stay in the provisioning state 'Accepted' for many hours. Sometimes they eventually go to 'Failed'. Is intermittent, sometimes they synchronize fully in about 30 seconds

Hello @Neil Smith, welcome to this moderated Azure community forum. I expect the Azure IoT Operations deployment is running successfully. What kind of data flow (which source and destination, and possible transformations) is deployed? Deploying a data flow takes some time (because these need to be merged on the edge with the current situation). I just finished this blog post about deploying data flows using Bicep scripts. There you can see how to deploy a basic data flow from local mqtt broker to local mqtt broker via Bicep. I can also recommend adding transformations step by step so you know for sure what is working and what is not. Please share your experience with more details so other community members understand the context better. If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

Azure IoT Operations Dataflow sync very slow

Accepted answer

Sander van de Velde | MVP 33,951 Reputation points MVP

2024-12-11T17:14:18.17+00:00

Hello @Neil Smith,

welcome to this moderated Azure community forum.

I expect the Azure IoT Operations deployment is running successfully.

What kind of data flow (which source and destination, and possible transformations) is deployed?

Deploying a data flow takes some time (because these need to be merged on the edge with the current situation).

I just finished this blog post about deploying data flows using Bicep scripts.

There you can see how to deploy a basic data flow from local mqtt broker to local mqtt broker via Bicep.

I can also recommend adding transformations step by step so you know for sure what is working and what is not.

Please share your experience with more details so other community members understand the context better.

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.
Please sign in to rate this answer.
Neil Smith 20 Reputation points

2024-12-11T17:56:44.4466667+00:00

I didn't notice any error message and didn't go delving in to container logs, I just saw state as Failed, I don't have any failed at the moment so can't check for error messages.

Thanks for your blog post looks very interesting, perhaps I'll make them in Bicep in future. I made a simple dataflow, the source is the default MQTT instance, I then add a couple of properties to the json and the destination is an event hub on azure. I currently make them using the web front end, iotopertions.azure.com. I just had a fairly simple modification stuck in the Accepted state for 6 hours before changing to Succeeded

Sander van de Velde | MVP 33,951 Reputation points MVP

2024-12-11T18:24:21.04+00:00

Hello @Niel Smith,

my experience is that a data flow update, even with transformations that do not make sense, take less than 30 seconds (at least less than a minute).

You could experiment with the data flow by adding or deleting some of the transformations. Perhaps you can gain and share more insights this way.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure IoT Operations Dataflow sync very slow

0 additional answers

Your answer