> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/troubleshooting/import-finished-successfully-but-data-was-truncated-warning.md).

# "Import finished successfully, but data was truncated" warning

After running a data flow, the following warning is shown:

```
Data was partially imported because you have exceeded your current plan limit. Import finished successfully, but data was truncated.
```

Warning samples:

{% hint style="warning" icon="triangle-exclamation" %} <mark style="color:$tint;">**Data was partially imported because you have exceeded your current plan limit**</mark>

<mark style="color:$warning;">Import finished successfully, but data truncated because your dataset contains more than</mark> <mark style="color:$warning;">**10,000**</mark> <mark style="color:$warning;">rows.</mark>\ <mark style="color:$warning;">Please upgrade your plan to import more than 10,000 rows.</mark>
{% endhint %}

{% hint style="warning" icon="triangle-exclamation" %}
**Import finished successfully, but data was truncated**

<mark style="color:$warning;">One or more of your data sources contain more than</mark> <mark style="color:$warning;">**100**</mark> <mark style="color:$warning;">rows, which exceeds your current plan's limit. Please upgrade your plan to import</mark> <mark style="color:$warning;">**100**</mark> <mark style="color:$warning;">rows per data source.</mark>
{% endhint %}

This warning indicates you have hit the [Data Volume limit](/functionality/coupler.io-features-and-limits.md#data-volume-l1bbp) . This limit differs[ per billing plan](https://www.coupler.io/pricing).

There can be an edge case where you receive this warning even when your rows in the destination file are within your limit.

**Why does it happen:**

**There are 4 stages your data undergoes when you set up an integration in Coupler.io:**

* Step 1 - Sources setup
* Step 2 - Data Sets (Transformations)
* Step 3 - Destinations setup
* Step 4 - Flow Settings

<figure><img src="/files/NC2hg6rdP5N549zCmO3w" alt=""><figcaption></figcaption></figure>

This edge case may happen when you reduce your dataset during step 2 - Data Sets, but your original dataset from step 1 - Sources is bigger.

Coupler.io fetches your data fully based on the parameters you've set in step 1 - Sources setup, before showing your data on step 2 - Data Sets. In the Destinations, you see the data that matches the data in step 2 - Data Sets.

This is why your Data Volume limit is getting reached. Because internally, Coupler.io still uses resources to pull all your data during the first stage. The filter is applied later, in the second stage.

<details>

<summary>Example scenario</summary>

You are on the free plan with a 100 rows/run Data Volume limit.

You are running 2 Campaigns in Facebook Ads and want to pull insights for 1 Campaign for the last week. On Step 1 - Sources setup, you used only the date settings. On Step 2 - Data Sets, you applied a filter by campaign name and ran the data flow to a spreadsheet.

<div align="left"><figure><img src="/files/ueDQkc3tuimW4JAFZxmH" alt="" width="375"><figcaption></figcaption></figure></div>

The destination spreadsheet showed 70 rows of data, yet you received the "Import finished successfully, but data was truncated" warning.

Why? Your original dataset **before Transformations** was 150 rows, as it had data for all your Facebook Ads Campaigns for the past week.

To not receive this warning, you can apply all filters on Step 1 - Sources setup instead, so your original dataset is under 100 rows. In our example case, you can apply both date filters & filter by campaign name there.

<div align="left"><figure><img src="/files/5sS7Yzx0nXitjG70FaQZ" alt="" width="375"><figcaption></figcaption></figure></div>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/troubleshooting/import-finished-successfully-but-data-was-truncated-warning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.