Share all details about your problem, including any error messages you may have received.
We are attempting to run an account aggregation task for a web service connector that experiences intermittent failures. The failures occur on different accounts each run-through, so instead of tanking the entire aggregation, we’d like to allow a set amount of failures.
To do so, I’ve enabled “haltOnMaxError” with a value of 100, but it does not seem to have changed anything. The task result object still only lists a single error, and there doesn’t seem to be the expected message that the documentation calls out:
If the database is available, the task result contains a message indicating that the task was terminated due to excessive errors.
Is there another setting I need to enable somewhere? Maybe on the application?
Or am I just not reading the task result correctly?
I am unable to gather logs for the exact same scenario. The production instance of this application is made up of a large volume of accounts, the failures are intermittent, and the account aggregation takes an extended period of time to run.
What I have is logs from our test server. I updated the maxErrorThreshold to two, and then edited the access token to be incorrect which triggered a failure immediately.
In my opinion, setting “haltOnMaxError”: true and configuring “maxErrorThreshold” will not be effective for connector exceptions thrown during Aggregation like you added incorrect access token. These settings are applicable to iteration-level errors
These settings are applicable to iteration-level errors
Is this information present anywhere in the documentation? I am not sure how I would have known this.
Would it be possible to capture the error from the API in an After Operation rule and throw it as an error that would be recognized by the “haltOnMaxError” setting?