Return the full detail of one data import: per-batch status, progress, record counters, error detail and category, rejected rows and a deep link to the run in the Qobra web app.
Return the full detail of one data import, including its per-batch breakdown.A list_imports row plus configs — one entry per resource batch, each with its
own status, progress, record counters (created / updated / deleted / skipped),
error state, the connection it synced from and the rows it rejected or skipped
(the first 20, each with its reason). Reach for it after list_imports surfaces a
run whose outcome you need to explain, e.g. why an integration refresh failed or
why some users did not come in. You only see imports that touched a resource
type you may read; an import whose every resource type is outside your
permissions is reported as not found.
Deep link that opens this import expanded in the Qobra web app, on the
history page of a resource type it touched. Null only for an import with no
batch yet, which no history page lists.
Per-batch breakdown of the import — one entry per resource batch, each with
its own status, progress, record counters and error state. Only the batches
of resource types you can read are listed.
How the data reached Qobra for this batch: ‘integration’ (a CRM sync),
‘api’, ‘csv’ (a file upload) or ‘bulk_action’. One of: integration,
api, csv, references, provisioning, bulk_action.
The connection this batch synced from — one run can bundle several. Null
for a CSV upload, a bulk action, an API push tied to no connection, or a
connection since removed.
Why the connection failed, when the error came from the integration:
‘authentication’ (credentials rejected, reconnect it), ‘permission’ (the
connected account lacks access), ‘configuration’ (a setting, query or
object the customer set up is wrong or missing), ‘rate_limit’ (too many
requests, retry later), ‘unavailable’ (the integration is down or
answered unreadably), ‘invalid_request’ (the integration rejected the
request itself) or ‘unknown’. Null for an error raised inside Qobra, or
one recorded before categories existed. One of: authentication,
permission, configuration, rate_limit, unavailable,
invalid_request, unknown.
What the batch did within its resource_type. A user import names the
part of the users it imported: ‘users-attributes’ (the users and their
attributes), ‘hierarchy’ (who manages whom) or ‘groups’ (group
memberships). A bulk action names the action it applied — on users:
assign_manager, assign_licence, change_role, change_currency,
change_calculation_currency, set_attribute, assign_group, revoke_access,
send_invitation; on data-table records: edit_records, reset_records,
activate_records, deactivate_records, delete_records, change_name_field.
Null for any other batch.
How many rejections the import kept for this batch: one per rejected
row, except a record_range, which stands for a whole chunk of records.
It keeps the last 100 only, so when rejected_rows_truncated is true
there were more. For the number of records a batch did not apply, read
number_of_records_skipped.
The first 20 rows the import kept, in the order it recorded them, each
with its reason. When rejected_rows_truncated is true, the import had
already dropped older rows, so these are not the batch’s first
rejections. The row’s own source values are never included; the import’s
resource_url opens the list the web app shows.
What was rejected, by kind. ‘line’: a line of a CSV file or a record
of an API payload, by position. ‘user’: a user batch’s attribute
error, or a user a bulk action failed on. ‘group’: a group a bulk
action failed on. ‘record’: a record a data-table bulk action failed
on. ‘record_range’: a whole chunk of records a data-table bulk
action failed on at once. Null when the import recorded nothing to
locate the row by (a quota row, whose source values are never
served).
