---
title: "Data audit limitation"
url: "https://help.tabidoo.cloud/en/article/data-audit-limitation"
language: "en"
last_updated: "2026-03-11T06:40:05.618Z"
---

# Data audit limitation

What to do if your audit data grows too large?

## Principle

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:

![](https://cdn-assets.productfruits.com/d0734191-631b-4db3-af04-f05d903c4878)

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](https://help.tabidoo.cloud/en/article/user-account-settings) 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**

![](https://cdn-assets.productfruits.com/695c70c7-de44-44c2-828d-308429f81c13)

*Setting - for changing the table properties*

![](https://cdn-assets.productfruits.com/7c70c012-d857-4884-89bf-109611daccb8)

*Audit settings*

* * *

#### **Disable audit for API or scripting calls**

####   
You can also prevent audit records from being created during specific operations.  
 

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

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

> ![](https://cdn-assets.productfruits.com/436a15ed-9b9a-487a-8d51-38ea837e78ef)
> 
> Storing unnecessary data uselessly increases resource requirements.

* * *

#### **Using Scripts to Delete Audit Data**

If you need to delete audit records for specific tables using a script, you can use the **doo.functions.audit** function.

👉 See more details here: [Using doo.functions.audit to delete audit records](https://help.tabidoo.cloud/en/article/doofunctionaudit)

  
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**.