BP Client, notify when DB prevents logging

[Walter.Koller]

Currently (BP 6.9) when DB file size reaches its limit (or disk size or whatever might prevent writing new records) the BP environment might sill be up and running but new session logs are not created.

We had the case when one of our DB was with size quota and when reaching the max size following happend:

• release imports failed (with DB error message, which is fine and expected)
• Scheduler kept running and executing processes
• Sessions logs were not created
• Audit logs were written (but probably because they still fit in existing free space)

In order to comply with IT security, internal audit and industry regulations, it is obligatory to have logs created in any case. Not being able to write logs should not be ignored by Blue Prism but users has to be notified.

Possible options:

• write the error to session log (in hope a single record would still fit in free space but as well very likely run into the same problem as the execution logs)
• write an error in audit logs (might also run into no space issue but in our case it was still working. Bigger issue is the audit logs have to be actively monitored otherwise it will go unnoticed)
• terminate the process and show it as terminated in Control (currently processes might still run or fail according to their logic and not because of DB issues)
• ...

Probably terminating the execution is the most viable option before processes could run for days (in our case) without creating any logs.