I have a record type configured to sync data sourced by a web service with a scheduled sync that runs once a day. Everything works seamlessly as long as the webservice returns data as expected.
IF in case the daily sync fails for some reason (for example: a connection timeout when calling the webservice) then all the record data is removed from Appian causing errors in the rules and interfaces that use this record type. Ideally, I would expect Appian sync to fail BUT retain the last synced data instead of cleaning it up and causing the record type to be inaccessible.
Is there a way to work around this issue other than by writing additional logic in the record source expression to backup data before calling the integration and then restore if something goes wrong?
Would love to hear your suggestions/ideas.
Discussion posts and replies are publicly visible
One work around you could try if it fails intermittently:
You could set up your service so that if the web service call returns an error, it just drops the batch that failed. one way to do this is to add logic in your expression to insert a dummy row that has information about the failed item like this:
ri!batchNumber > 100,
id: "999999" & ri!batchNumber,
summary: "Batch Failed",
Thanks for looking into this. In this particular business case we do not sync in batches because the dataset is not that huge.
And for your question on how often this can occur - I don't have a definite answer for that but I can say that if it does occur then we have an unstable application the entire business day until someone manually starts another sync or the next scheduled sync runs automatically.
I really like the workaround that you suggested where we set up logic to query the source if the a!queryReordType() fails. I did not notice that a!queryRecordType() had a "success" parameter that indicates a sync failure.
By the way, one option that was in my mind was to backup the recordData in a local variable and restore it if the sync fails. But I noticed that Appian does not allow running smart service functions like a!queryRecordType() in a "Record Source" expression. Maybe something to keep in mind for others following this discussion!
Thanks for suggesting a solution, I think this workaround will fit our design.
Peter Lewis I think that we should be able to define the sync expression in a way that the data in cache is not deleted in case something goes wrong. I happens all the time that the other systems are not available.
© 2021 Appian. All rights reserved.