Entire Sync Duration: 13 hours, 12 minutes

Sync Start: 06/18/2021 6:22:14 AM

Sync End: 06/18/2021 7:34:11 PM

Status: Failure

Reason: java.util.concurrent.ExecutionException: java.lang.RuntimeException: javax.ws.rs.WebApplicationException: { "error": { "code": "account_invalid", "doc_url": "https://stripe.com/docs/error-codes/account-invalid", "message": "The provided key 'sk_live_51*********************************************************************************************IXiP' does not have access to account 'acct_abcde' (or that account does not exist). Application access may have been revoked.", "type": "invalid_request_error" } }

Extract Time: 9 hours, 36 minutes

Process Time: 3 minutes, 6 seconds

Load Time: 3 minutes, 26 seconds

Data Volume: 112 MB

//

 

When we have several thousand connected accounts, if for some reason, a connected account is not accessible, the sync fails
after 10-14 hours of processing.
My question is whether this can be avoided. If a connected account is not accessible( perhaps it is deleted or probably some other reason),
can the sync skip data pertinent to that account and complete the syncing process?

For example, if the 999th connected account is not accessible out of a total of 1000 connected accounts, the sync fails after 10 hours of processing.
Instead, can it skip the 999th connected account and try to do work on the 1000th connected account and finish all the work that was done
for all the connected accounts except the 999th one?

We're seeing sync failures across tables every few days and we'd like to avoid it.