The exception email message you get when a Flow failed in its execution is probably the most handy tool one can have when troubleshooting a Flow (especially in Prod environment). It has a ton of debug information - sometimes almost too much - and usually organized in a quite usable way. However I did notice that some Flow exceptions generate no specific information in the email, which looks apologetically generic
When that happens I usually would go for the next best thing - our best friend, debug logs. Fortunately I noticed this kind of generic exceptions is often related to a straightforward problem: a field is referenced from a record variable without being set first, either by Get Record or Assignment, which is very similar to the infamous "SObject row retrieved via SOQL without querying the requested field" in Apex. So, check for the field reference mishaps first next, fellow Flow warriors...
No comments:
Post a Comment