commit object not committed on custom without rollback

0
I have the following situation in a microflow where when an error occurs on ‘execute list’ it should commit the object ‘ErrorLog’ but it seems not to be saving anything?
asked
1 answers
0

Joni

When an error is encountered in a list operation, the objects will not be committed.  The ‘without rollback’ part of your error configuration means that any database actions completed prior to the list operation will not be rolled back.

Hope that helps,

Mike

answered