Hi @kapa.ai we are using the paystack connector in South Africa, and we have noticed an increased ad hoc sync failure that resolved itself usually on the next run. We are using this marketplace version

Paystack v1.1.18

Hi! Thanks for reaching out about your Paystack connector issues. Based on the available information, here are a few things worth noting: Your Connector Version You're running Paystack v1.1.18 (released 2025-10-29). The latest available version is v1.1.28 (released 2026-03-31). There have been several dependency updates since your version, primarily updating the

airbyte-cdk

library. [Paystack Changelog] It would be worth upgrading to the latest version to benefit from these dependency improvements. Ad Hoc Sync Failures That Self-Resolve The intermittent failures you're describing — where a sync fails but resolves on the next run — are consistent with transient errors that Airbyte handles via its heartbeat and retry mechanisms. Some known causes include: • API rate limiting: The source API may be rate-limited for a period longer than the configured threshold. Airbyte tries to handle this per-connector, but rate limits aren't always predictable. [Heartbeats] • Asynchronous API responses: Certain API sources take an unknown amount of time to generate responses, which can trigger heartbeat errors. [Heartbeats] The Paystack connector documentation also notes: > "The Paystack connector should not run into Paystack API limitations under normal usage. Please create an issue if you see any rate limit issues that are not automatically retried successfully." [Paystack Source] Recommendations 1. Upgrade to the latest Paystack connector version (v1.1.28) to ensure you have the most recent CDK fixes. 2. Monitor whether the failures correlate with specific streams or times of day, which could point to rate limiting. 3. If the issue persists after upgrading, consider filing a GitHub issue or reaching out to Airbyte Support with details about the error messages you're seeing. The knowledge sources don't contain specific information about issues unique to South Africa or regional API behavior differences, so I can't speak to that aspect directly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai if going from version 1.1.18 -> 1.1.28, do I need to do anything on the backend if self-managing my airbyte instance? or can I just amend the version on the frontend docker image tag?

Since you're going from v1.1.18 → v1.1.28, this is a patch-level update only (both are within the 1.1.x range), which means no breaking changes are expected. For self-managed Airbyte instances, here's what you need to do: Steps to Update 1. Update the local connector image in your registry first: ◦ Go to Workspace settings > Sources ◦ Find the Paystack connector in the list (Airbyte will show both the current in-use version and the latest available) ◦ Click Change to update to the latest available version [connector-updates] 1. Opt-in to the update via the settings page (all versions on self-managed are opt-in). Once you opt-in, patch updates are applied immediately and globally to all connectors of that type in your instance. [connector-updates] Do you need backend changes? Since this is a patch update, no schema changes or data pipeline adjustments are required. You should not need to clear data or refresh schemas — those steps are only necessary after a connector upgrade that introduces a breaking change. [connector-updates] The knowledge sources don't explicitly confirm whether simply amending the Docker image tag directly (bypassing the UI) is a fully supported workflow, so I'd recommend using the Airbyte UI settings page as described above to ensure the update is properly registered within Airbyte's internal registry. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.