Connections, auth and API

Why does my dataset API call or integration process only part of my records?

List APIs page their results, and integration actions cap rows at 100 or 200. Page through the API, or batch larger loads.

Fix

Short answer: The API returns records one page at a time, and integration steps have fixed row limits. Page through API results, and split large loads into batches.

Why it happens

  • List all dataset records returns 10 records per page unless you set page_size.
  • An iteration processes only the first 100 records of its source and ignores the rest.
  • The dataset connector's Bulk update dataset records and Find records from a dataset actions handle up to 200 records.
  • The process connector's Search an item action returns up to 100 items.
  • Filters on the dataset or view reduce what's returned.

How to fix it

  1. Check the dataset and view for filters first.
  2. For the API, add page_size and page_number and loop through the pages.
  3. In an integration, narrow the rows with filters or conditions so each run stays under the limit.
  4. For larger loads, use the dataset batch API, which takes up to 500 records per call. See API and SDK documentation and the Kissflow Dataset connector limits.
  5. If an external API returns pages, iterate over each page separately.
  6. To repeat an action N times, give the form a table with N rows and iterate over the table. An iteration loops over a list of rows, not a number.

Important

The 100-record iteration limit is fixed, and the docs offer no way to raise it. Design for batches instead. The dataset limit of 50,000 rows and 100 columns is a soft limit. If you need more, contact Kissflow support with the dataset, the size you need and your use case. See creating a dataset and Loop action in control connector.

Related answers