"Import finished successfully, but data was truncated" warning

After running an importer, 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:

This warning indicates you have hit the Data Volume limit (previously - Max import size limit). This limit differs per billing plan

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


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

  • Step 1 - Data Source setup 
  • Step 2 - Transformations
  • Step 3 - Data Destination setup
  • Step 4 - Schedule setup

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

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

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.

Example scenario:

You are on a plan with a 1000 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 - Data Source setup, you used only the date settings. On Step 2 - Transformations, you applied a filter by campaign name 

and ran the importer to a spreadsheet. 

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

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

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

See more about how to filter Facebook Ads data on Step 1 here.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.