Attio was unavailable

What you see

On the run page, open the Errors tab. Under the object that failed, a row is titled "Attio was unavailable". Below it, one line counts the records that were not imported. The reason line reads: "Attio returned a server error while this row was being written." The row lists the source record ids that did not import; with more than three, they sit behind a Show line that gives the count. "Technical detail" holds the failed request, its HTTP status and the start of Attio's response.

Why it happens

Shuttio sent the row to Attio, and Attio answered with a server error: any HTTP status of 500 or higher. Shuttio treats every such status the same way; the status alone does not say what caused it. Shuttio marks the row as failed. Server errors like this are usually transient.

How to fix it

1. Open the row's "Technical detail". With more than three records, it sits inside the Show line. It shows the HTTP status and the start of Attio's response. Quote it if you email support.
2. Press "Retry all errors" on the Errors tab. It runs only the failed items again, matches records that already exist instead of duplicating them, and is free. How Retry all errors works.
3. If the run is paused, press Resume first, or Reconnect if the reason starts with "Reconnect".

If the same rows fail again on a retry, email help@shuttio.com with the migration number from the run page's side rail.