Recently we've had issues with a few individual cards failing causing the flow to create data in an inconsistent way. I didn't catch the issue quickly enough to prevent the problem from happening ~500 times. We had to write some code on our end to match between salesforce and google to delete the folders that were out of place
How does everyone else deal with this kind of thing?
Flow detail: Our flow creates a google drive folder based on some conditions with salesforce accounts. If conditions are met -> Create Google Drive Folder -> Push Google Drive Folder ID back to salesforce. This is the worst time for our flow to fail as between these flows we have a folder in google drive that's not tracked anywhere. This is when the salesforce card failed.
*We have multiple salesforce accounts listed in the Accounts Section, not sure if this contributed as one of the accounts may have been authed properly while the other wasn't.
Solutions put in place:
Error handling on cards. Is there a way to default all of our cards to retry the connection x number of times and trigger another flow with predefined values? Right now we setup our error handling like this:
*The flowName variable we have to setup for each flow, could we get this added to the Context of the flow instead?
*This flow just alerts slack to let us know there's an issue otherwise we have no idea there's a problem which is one of the biggest issues we have, we don't want to think about Azuqua at all unless it needs us to fix something.
Dependency checking at the beginning of flows. For our flow that had the google drive problem we added a SalesForce Read and Google Drive Read card before the initial folders are created to prevent the same issue we had before of ~500 folders being created and duplicated that had to be cleaned up. Now at least the flow will fail before it creates hanging objects.