Skip to main content
Documentation
Docs overview

Diagnose connection or pipeline issues

Separate authorization health from import settings, then inspect Amazon run history and errors.

Before you start

Sign in and select the affected workspace. You need access to its Connectors and Pipelines pages; ask someone with workspace settings permission to make changes you cannot save.

A connector holds credentials or authorization. A pipeline uses a connector to import data. A connection can exist while its pipeline is paused, and a working authorization does not prove that a particular report has been imported.

Check the connection

  1. Open Workspace Settings → Connectors.
  2. Find Amazon SP-API or Amazon Advertising API, then choose Manage.
  3. Identify the connection and read Status, the reason beneath it, and any suggested remedy. Check Marketplaces for SP-API or Profiles for Advertising to make sure you are inspecting the intended account.

The connection status words mean:

  • Working: the connection is reported as working.
  • Needs attention: read the accompanying warning and remedy.
  • Failing: read the failure and the action offered for that connection.
  • Not checked: the connection exists, but no result has been reported. This is not confirmation that it works.

Follow the displayed reason. A failing Seller connection offers Reauthorize the seller account. Advertising failures can offer Reauthorize the Advertising account; a missing profile calls for an Amazon login with an advertising profile, while a payment warning directs you to add a valid payment method in the Amazon Ads console.

Use the Seller Central or Advertising guide for the relevant authorization flow. Removing a connection is not a general diagnostic step.

Check the pipeline

  1. Open Workspace Settings → Pipelines and find Amazon.
  2. Check whether it is enabled. If Enable is offered, use it only when imports should be running: it starts setup for a new pipeline or resumes a paused one.
  3. For an enabled pipeline, inspect the Amazon Selling Partner and Amazon Advertising summaries separately. Read Last success, Next run, and Latest error where shown.
  4. Open Settings to reach Amazon Configuration. Check the selected stores and data on Defaults and the enabled-store tabs. A store can have its own overrides, so inspect the affected store as well as the defaults.

When a summary says No recent runs, No run scheduled, or that the next run is waiting, investigate the configuration and history. If run state could not be loaded, reload the page. Missing run details are not evidence that the pipeline is healthy.

Inspect run history

Choose Run history beside the affected summary. Selling Partner and Advertising have separate histories even though their settings share the Amazon pipeline.

The history shows Completed, Failed, Retrying, Running, Scheduled, or Skipped for each recorded run. Where a pipeline has several parts, narrow the list to the relevant part; use the older-page link to inspect earlier records.

Read the item key, time key, due/completed/error times, error count, and full recorded error. The item key identifies what a run fetches; the time key identifies the period it covers. Times are UTC.

Run history is a display of recorded work. It does not start or retry a run. A completed run confirms that recorded run completed; it does not prove that every expected dataset or period is present.

What a successful check tells you

You have separated three questions: whether the authorization works, whether the intended stores and data are enabled, and what happened to the relevant import runs. Check the recorded runs for the affected data and period rather than treating a success banner or a recent success elsewhere as proof of completeness.

When to contact support

Contact support when the displayed remedy does not resolve the connection, run state cannot be loaded repeatedly, an expected run is absent, or failures continue after you check the selected data and stores.

Include:

  • the workspace, connection, and pipeline names;
  • the status and its displayed reason;
  • the affected data or period and the relevant UTC times;
  • sanitized error text from the run history.

Do not include passwords, access tokens, client secrets, or an unredacted dump of data.

Need help with your workspace? Contact support.