Erreur de flux / échec d'exécution de la notification

Question

Bonne journée.<\/P> J'ai une série de flux Power Automate pour notre plateforme Survey123. Beaucoup des rapports Survey123 soumis sont sensibles au temps et sont nécessaires pour poursuivre d'autres tâches au sein de l'entreprise. <\/P> Il arrive qu'un flux échoue à s'exécuter et je ne m'en rends pas compte avant que la direction ne se plaigne de ne pas avoir vu un rapport PDF spécifique.<\/P> J'essaie de trouver une solution pour être notifié (E-mail) si un flux échoue et/ou recevoir un rapport/log E-mail nocturne montrant la réussite de tous les flux ainsi que les flux ayant échoué ou contenant des erreurs.<\/P> Toute orientation serait appréciée.<\/P>

Akshay Harshe · Answer

Noting specific, I think in general using scopes was the highlight for me. I usually dabble into Esri actions and triggers and some automation for our testing but my life isn't dependent on creating automation and how you explained in the post above was really great.

abureaux · Answer

I'd be happy to put something together. Is there a specific aspect that would best qualify?

abureaux · Answer

Depending on how you currently do error handling and recovery, you may wish to do something similar to me.

Basically...

* Ditch the "When a survey response is submitted" step and replace it with a "Schedule".
* In your survey, add a question with a field dedicated to process automation.* For me, I use S123 templates with a bunch of standard questions already added so I don't need to duplicate work.
* One of those questions is a calculate called "prime_process" with this calculation -- if(1=1,'FALSE','') -- which ensures that no matter when the user opens the survey (e.g., if they resubmit), this question will always result in a FALSE outcome. (Minor note, but this is a text field, not a binary field. I just happen to be using "FALSE" and "TRUE")

* In your flow, use the Arcgis "Get data from feature layer" connector, set Output format to "JSON", and the Where clause to something like prime_process='FALSE'

* Then you need two simple things (in this order):* Arcgis' "Update a record in a feature layer" or the "batch" equivalent (depends on your workflow - but batch is probably best in most cases) to update all items with, for example, prime_process="TRUE". This ensures you mark the submissions as "processed" so you don't end up reprocessing them.
* Arcgis' "Update a record in a feature layer (batch)" (I can't think of any reason to not use batch here) within your error handling step. This one will reset all failed jobs to, for example, prime_process="FALSE". This ensures they are reprocessed on the next cycle.

I'm sure I made this sound harder than it really is. But this is (generally speaking) the best process automation solution I've found for this work. It ensures 1) nothing is missed, and 2) if there is an error, an automatic re-try occurs.