Common Issues

Connection issues

API key is rejected or returns an authentication error

Double-check that you copied the full API key from Codefresh — truncated keys are a common cause of auth failures. In Codefresh, go to User Settings → API Keys and regenerate a new key if you're unsure. Make sure the key has not been revoked or expired. Paste it fresh into the Coupler.io source settings without any leading or trailing spaces.

Connection succeeds but returns no data

Check your start date setting. If the start date is set too far in the future or beyond your account's data retention window, the sync will return empty results. Use the date picker to set a start date within the range where you know builds or events exist.

Missing data

Analytics reports entity returns empty results

Analytics reports require both report granularity and report date range to be set. If either is missing or the date range doesn't match any completed reporting periods, the entity will return no rows. Make sure your date range covers at least one full granularity period (e.g., a full day for daily granularity).

Builds from a specific pipeline are missing

Codefresh build history is scoped to your account. If a pipeline was deleted, its build records may no longer be accessible via the API. Also confirm that the API key belongs to an account that has access to that pipeline — builds from sub-accounts or teams you're not a member of won't appear.

Audit logs don't go back far enough

Audit log retention is controlled by your Codefresh plan and account settings. Coupler.io can only retrieve what Codefresh exposes via its API — if events older than a certain date aren't returned, they've likely been purged from Codefresh's retention window.

Permission errors

Certain entities return a 403 or permission denied error

Some Codefresh entities (like Accounts or Account settings) require admin-level access. If your API key is tied to a non-admin user, you'll get permission errors on those entities. Generate an API key from an admin account, or limit your data flow to entities your current user has access to.

Data discrepancies

Build counts in Coupler.io don't match what I see in the Codefresh UI

The Codefresh UI may apply default filters (e.g., showing only the last 30 days, or filtering by a specific pipeline). Your Coupler.io data flow pulls based on the start date you configured with no additional filters applied by default. Adjust your start date or filter the exported data in your destination to match the UI view you're comparing against.

Analytics report metrics differ from in-app analytics

The in-app analytics dashboard may use a different aggregation method or exclude certain build types (e.g., cancelled builds). Check that your report granularity and date range in Coupler.io exactly match the period shown in the Codefresh analytics UI.

Rate limits

Sync fails or slows down with large build histories

Codefresh API rate limits apply based on your account tier. If you're syncing a very large build history (months of data on a busy account), the initial sync may hit rate limits and slow down. Start with a shorter date range to get recent data first, then extend the range in subsequent runs.