Case Errors¶
Definition¶
When Atfinity evaluates a case and something goes wrong, it records what failed as a case error rather than stopping the case. Most come from rules, whether they run in the Case Manager or as a scheduled rule, and the rest from producing a document or from an integration.
Each error records when it happened, the case or the instance it belongs to, and a message describing what failed.
The configuration area lists every error in the tenant under Evaluation Errors, and lets you delete all of them or only those older than a week. A single case shows its own errors in the Case Manager, which needs the View Case Error Log permission rather than access to the configuration.
Instance errors¶
Info
New in Atfinity 18.
An error raised outside any case, while a manual instance action or a scheduled rule runs on an instance, is recorded against the instance and has no case. It also records who ran the manual instance action or pressed Execute on the scheduled rule, and nobody for a scheduled rule that runs on its own. A failed custom API request the run started is recorded the same way, after the run itself has returned. An instance keeps one entry per distinct error: when the same error happens again, its entry moves to the latest time and the latest person instead of being added twice.
An instance shows its own errors on its Error Log tab, which needs the same View Case Error Log permission. Instance Errors in the configuration area lists the errors of every instance, and deletes them without touching the errors of cases. Evaluation Errors lists instance errors as well, so deleting there also empties the Error Log tab of every instance.
Example¶
A rule subtracts a number from a piece of information of type string:
Subtracting from a domicile is impossible, so the rule stops and the case error names the rule and the failure.
Adding instead of subtracting does not fail: + concatenates when either side is a string, so p.domicile + 1 gives
you the domicile with a '1' on the end.