Tabidoo stores audit data automatically to track changes in your application.
The retention period of audit records depends on your pricing plan. Audit history can be stored from 2 weeks up to unlimited time, according to the selected plan.
Besides the time retention, there is also a limit on the total number of audit records. The maximum number of audit records corresponds to the row limit of your application plan.
For example:
Pricing Plan
Maximum Audit Records
Standard
up to 50,000 audit records
This means that if your application plan allows 50,000 rows, the same limit applies to the number of stored audit records.
When can the audit grow too large?
If you work with Tabidoo mainly using manual inputs, it is very unlikely that you will reach the audit limit.
However, the situation can change if you use:
Scripts
Workflow Automation
Frequent API operations
These processes can generate a large number of audit records in a short time, which may exceed the allowed limit.
If the number or size of records in the audit table exceeds a certain amount, the application will start displaying a warning:
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 resolve 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.
In the table settings, you can:
disable audit logging
delete existing audit records
Table settings → Audit (history) settings
Setting - for changing the table properties
Audit settings
Disable audit for API or scripting calls
You can also prevent audit records from being created during specific operations.
