フローエラー／実行失敗通知

Question

こんにちは。<\/P> 弊社のSurvey123プラットフォーム用に一連のPower Automateフローを作成しています。提出される多くのSurvey123レポートは時間に敏感であり、会社内の他のタスクを進めるために必要です。 <\/P> 時々フローが実行に失敗していることに気づかず、管理部から特定のPDFレポートが見当たらないと苦情が来るまでわからないことがあります。<\/P> フローが失敗した場合に通知（Eメール）を受け取る方法や、すべてのフローの正常完了および失敗／エラーフローを示す夜間のEメールログ／レポートを作成する方法を検討しています。<\/P> 何かアドバイスをいただけると幸いです。<\/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.