Data audit limitation

What to do if your audit data grows too large?


Tabidoo stores all Audit data indefinitely. For unlimited time. (Its display, however, depends on the pricing plan.)

Anyway, unlimited time could not mean unlimited amount of course. If you work with Tabidoo using manual inputs, you will probably never hit a limit in the audit.

The situation changes if you use scripts or Workflow Automation. Here it is possible to generate a huge number of records about history. Which you will probably never need.

If the number or size of records in the audit table exceeds a certain amount, the application will start displaying a warning:

The audit table for the application is too big.

Please check the documentation or contact us to avoid any issues with the audit.

If the system continues to store large amounts of data into history, the second constraint is reached. Here, the oldest audit records are already being deleted.

How to get out of this?

Show audit size

The size of the audit data is visible in the same place as the data usage of the applications.

Suppress saving of audit data

If you do not need to monitor the history over a table, it is possible to disable the history completely. 

Here, you can disable the audit for the table. In the same place, you can delete existing audits as well.

Setting - for changing the table properties

Audit settings


Or you can disable history for individual API/scripting calls.

await doo.table.createRecord('Table Name', fields, { skipAudit: true })

Keeping audit data low helps to improve system speed and responsiveness. 

Storing unnecessary data uselessly increases resource requirements.

If for any reason you need to keep your history above the normal limit, please contact us. We will be happy to set an individual limit for you.