You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few ideas I have to enhance the flow logging experience:
Capture the InterviewGuid
It would be great if the flow InterviewGuid could be captured on LogEntry__c records. This would make it really easy, for example, to search for and find the correct error email received in the event of an exception.
Capture the element name when logging on a fault path
Not sure if this is possible, but when using the "Long Entry" action on a fault path in flow, we can capture the flow FaultMessage. But we don't get any info on what element triggered the fault path when reviewing the logs. Of course, we can manually assign this value in the message field. But, if this can be automatically captured, then it means we can use a single "Log Entry" action and connect all fault paths to it, rather than having to customise each fault path to manually enter the element name.
Capture the flow fault email
This would trump both the above. If there was a way to capture the flow fault exception email and store the body on a Log Entry, that would be amazing. The reason being that these emails have a ton of great info making it very easy to debug errors. If it was already on the Log/LogEntry then this would make things even easier.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
A few ideas I have to enhance the flow logging experience:
Capture the InterviewGuid
It would be great if the flow InterviewGuid could be captured on
LogEntry__c
records. This would make it really easy, for example, to search for and find the correct error email received in the event of an exception.Capture the element name when logging on a fault path
Not sure if this is possible, but when using the "Long Entry" action on a fault path in flow, we can capture the flow FaultMessage. But we don't get any info on what element triggered the fault path when reviewing the logs. Of course, we can manually assign this value in the
message
field. But, if this can be automatically captured, then it means we can use a single "Log Entry" action and connect all fault paths to it, rather than having to customise each fault path to manually enter the element name.Capture the flow fault email
This would trump both the above. If there was a way to capture the flow fault exception email and store the body on a Log Entry, that would be amazing. The reason being that these emails have a ton of great info making it very easy to debug errors. If it was already on the Log/LogEntry then this would make things even easier.
Beta Was this translation helpful? Give feedback.
All reactions