What a retry inherits from the runs before it
const url = 'https://api.sloose.com/orgs/org_9f3c/imports/imp_4d1a/runs/run_7c2e/inherited';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.sloose.com/orgs/org_9f3c/imports/imp_4d1a/runs/run_7c2e/inherited \ --header 'Authorization: Bearer <token>'The records the run this one retries — and whatever that run itself inherited — already made, which this retry does not write again: gathered when the retry was authorised, so what a retry inherits does not change and does not depend on how long the runs before it are kept, or on whether the meter counted it as a retry. Newline-delimited JSON. The first line says what the run stands on — retried, the run it retries, and which of that run’s sources start over, because their file, or how the file is read, has changed since, so their rows are written again: { "retried", "startedOver": [{ "flowId", "label" }] }. A run that stands on none — one authorised without naming a run of this import that has ended, or a dry run — is answered that line alone, with retried null. Every line after it is one run record at attempt 0, of one of three kinds. inherited, for a row and module whose record the chain made: { "rowKey", "flowId", "rowNumber", "module", "recordId", "code", "keys", "patched", … } — code says how the chain made it (created or updated), keys the values it was indexed under for links and matches (less the fields its patches may have changed), and patched the fields its after-save patches filled. inherited with "phase": "patch", for an after-save patch that filled a field and put keys on its record: the same shape with target the field, recordId the record and keys the values the patch put on it, which a later row’s link or match may search on. And unanswered, naming no record, for a row and module whose create the chain sent and never heard back about, with nothing in the chain making the record since: it may have been made all the same, so the retry that makes it says the record may exist twice. Any member of the org may read it.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The org id the session was issued for. A token for one org can never read another.
Example
org_9f3cThe org id the session was issued for. A token for one org can never read another.
The import id.
Example
imp_4d1aThe import id.
The run id, from POST /entitlements/runs/authorise.
Example
run_7c2eThe run id, from POST /entitlements/runs/authorise.
Responses
Section titled “Responses”Newline-delimited JSON: what the run stands on and which sources start over, then each record inherited.
Examplegenerated
exampleNo bearer, or one that is expired, revoked or no longer resolves to a member.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}The bearer’s role is too low, or it was issued for a different org.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}No such import or run, or it is not visible to this session.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}A run’s inheritance is in storage this deployment cannot reach (code: NOT_CONFIGURED).
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}