MTA
11/24/2025, 4:49 PMkapa.ai
11/24/2025, 4:49 PMMTA
11/24/2025, 4:50 PMkapa.ai
11/24/2025, 4:51 PMpage, page_number, or offset) are being correctly injected into your POST request. If the API expects the page number or offset in the request body (not as a query parameter), make sure your paginator is configured to inject these values into the correct location (e.g., body_json or body_data). - Double-check the parameter names and their locations as required by the API documentation. If the API expects page in the body, but your connector injects it as a query parameter, the API will ignore it and always return the first page of results, causing the repeated data issue you’re seeing[Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting). 2. Verify First Request Behavior - Some APIs require the pagination parameter to be present even on the first request, while others do not. Make sure your configuration matches the API’s expectations. You may need to enable or disable "Inject Page Number on First Request" depending on the API[Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting). 3. Test with Different Page Sizes - You mentioned that changing the page size has no effect. This could indicate that the API is ignoring the page size parameter, or that it is not being injected correctly. Try testing with very small page sizes (e.g., 2–5) and verify if the response changes[Testing Pagination](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#testing-pagination). 4. Check API Documentation - Confirm the correct pagination method and parameter names. Some APIs use page, others use offset, and some may use a cursor. Using the wrong method or parameter name will result in the same page being returned repeatedly[Page Increment](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#page-increment). 5. Validate API Response - Manually test the API outside of Airbyte (e.g., with Postman or curl) using different pagination parameters to ensure the API itself returns different data for each page. ### Next Steps - Review your paginator configuration in Airbyte and ensure the pagination parameters are injected into the correct part of the POST request (body, not query, if required). - Check the parameter names and their values in the outgoing requests. - Test the API manually to confirm its pagination behavior. - Consult the API documentation for the correct pagination approach. If after these checks the issue persists, it may be necessary to share your connector configuration and a sample API request/response for further troubleshooting. For more details, see the troubleshooting section in the Airbyte docs: [Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting).MTA
11/24/2025, 5:15 PMkapa.ai
11/24/2025, 5:15 PMkapa.ai
11/24/2025, 5:16 PMpage, page_number, offset, etc.) are being injected into the correct part of the request. Since your API uses a POST call, the parameters may need to be in the request body (as JSON or form data), not just in the query string. The Airbyte Connector Builder allows you to specify where to inject these parameters: as request parameters, headers, or in the body. If the API expects the page number in the body but you are only sending it in the query string, the API will ignore it and return the same data each time[Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting). 2. Correct Parameter Names Double-check the API documentation to confirm the exact parameter names and their expected location. For example, if the API expects page or page_number in the body, but you are using page_size or only passing it in the URL, it may not work as intended[Page Increment](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#page-increment). 3. Manual API Testing Test the API manually (e.g., with Postman or curl) by sending requests with different page numbers or offsets. Confirm that the API returns different data for each page when the correct parameters are provided. 4. Connector Builder Configuration In the Airbyte Connector Builder, make sure you have: - Set the correct pagination mode (likely "Page Increment" or "Offset Increment"). - Configured the page size and starting page correctly. - Injected the page number/offset into the correct location (body, if required). - Used the correct field names as per the API documentation. 5. Stop Condition If the API always returns 200 rows, ensure your stop condition is set so that pagination stops when fewer than the page size is returned, or when there are no more records[Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting). Summary: The most likely cause is that the page number or offset is not being injected into the correct part of the request, or the parameter name is incorrect. Review your Connector Builder configuration and the API documentation to ensure alignment. If the issue persists after these checks, the knowledge sources recommend reviewing the API's requirements and testing with sample data to debug further[Pagination Troubleshooting](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#troubleshooting). If you need more specific help, please provide the exact configuration of your paginator in Airbyte and a sample of your request body.MTA
11/24/2025, 7:57 PMkapa.ai
11/24/2025, 7:57 PMkapa.ai
11/24/2025, 7:57 PMMTA
11/24/2025, 9:28 PMkapa.ai
11/24/2025, 9:28 PMkapa.ai
11/24/2025, 9:29 PMtrue when pagination should stop. You can use variables from the API response, headers, or other context to define this condition. Common patterns include: - When a boolean flag in the response indicates no more results: {{ response.more_results is false }} - When a cursor or token is missing or null: {{ response.pagination.next_cursor is none }} - When the data array is empty: {{ not response.data }} - When a specific link is missing in the headers (e.g., for GitHub's Link header): {{ 'next' not in headers['link'] }} - Combining multiple checks: {{ response.data|length == 0 or response.pagination.next_cursor is none }} You can configure this in the Connector Builder UI or in the YAML for config-based connectors. The stop condition ensures that Airbyte knows when to stop paginating, even if the API does not explicitly indicate the end of data in a standard way. For more details and examples, see the documentation on [Advanced Cursor Pagination Features](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#advanced-cursor-pagination-features) and [YAML Reference for CursorPagination](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/reference#/definitions/CursorPagination).MTA
11/24/2025, 9:33 PMkapa.ai
11/24/2025, 9:33 PMkapa.ai
11/24/2025, 9:33 PMoffset for subsequent requests based on the number of records it receives, and will continue until it receives fewer records than the limit you configured [Offset Increment - Connector Builder UI](https://docs.airbyte.com/platform/1.8/connector-development/connector-builder-ui/pagination#offset-increment) So, you do not need to manually specify a stop condition for offset pagination in most cases. Airbyte will stop fetching new pages when the API returns a page with fewer records than the limit. If your API behaves differently (for example, always returns the same number of records even when there is no more data), you may need to use a different pagination strategy or work with a custom stop condition, but this is not standard for offset pagination as supported by Airbyte's built-in paginator.MTA
11/24/2025, 9:36 PMkapa.ai
11/24/2025, 9:36 PMkapa.ai
11/24/2025, 9:36 PMRECORD or STATE messages from the source as "heartbeats." - If no heartbeat is received within the configured time (heartbeat-max-seconds-between-messages), the sync attempt is failed and restarted. - The default threshold is 3 hours, but it can be configured in the flags.yaml file. - The relevant configuration options are: - `heartbeat-max-seconds-between-messages`: Maximum allowed time between messages (default: 3 hours). - `heartbeat.failSync`: If true (default), the sync fails on a missed heartbeat; if false, it does not fail the sync[Technical Details - Heartbeats](https://docs.airbyte.com/platform/1.8/understanding-airbyte/heartbeats#technical-details). ### Troubleshooting Steps 1. Check Source Performance - If your source is slow (e.g., due to large data, slow queries, or API rate limits), it may not emit records frequently enough. Optimize your source or queries if possible. 2. Increase Heartbeat Threshold - If your syncs are expected to take longer between messages, consider increasing the heartbeat-max-seconds-between-messages value in your flags.yaml file to allow more time between heartbeats. 3. Check for API or Network Issues - If the source is an API, ensure it is not rate-limited or experiencing downtime. 4. Review Connector and Sync Configuration - Make sure your connector is configured to emit records or state messages regularly, especially for large or complex syncs. 5. Logs and Support - Review the Airbyte logs for more details on where the process is stalling. - If the issue persists, and you are using Airbyte Cloud, you can reach out to Airbyte Support for further assistance[Heartbeats - Known Causes](https://docs.airbyte.com/platform/1.8/understanding-airbyte/heartbeats). Summary: The error is due to the heartbeat timeout. You can address it by optimizing your source, increasing the heartbeat threshold, or reviewing your connector configuration. If the problem continues, consult the logs or contact support for deeper investigation.MTA
11/24/2025, 9:40 PMkapa.ai
11/24/2025, 9:40 PMkapa.ai
11/24/2025, 9:41 PMMTA
11/25/2025, 10:24 AMkapa.ai
11/25/2025, 10:24 AMkapa.ai
11/25/2025, 10:24 AMfetch parameter (and its value, such as criteria) in your API request, you should not use the Record Selector, Extractor, or Field Path for this purpose. Instead, you should configure this as a request parameter in your connector configuration. In the Airbyte Connector Builder, you can add query parameters to your requests in the generic parameter section at the bottom of the stream configuration form. Here, you can specify key-value pairs for query parameters, such as: yaml request_parameters: fetch: criteria sort: asc This will ensure that every request sent to your API includes ?fetch=criteria&sort=asc in the URL. - Record Selector is used to specify the path in the API response where the records are located (e.g., data.items). - Extractor and Field Path are used for extracting data from the response, not for configuring request parameters. For more details on how to configure query parameters in the Connector Builder, see the documentation on [custom parameter injection](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#custom-parameter-injection). Summary: Add the fetch parameter in the request parameters section of your stream configuration, not in the Record Selector, Extractor, or Field Path. This will ensure the API receives the expected query parameter in each request.