Results and history

The result grid

One line per row, with what happened to it. The tabs across the top narrow the view:

All rows	Everything, in file order.
Created/Updated	The successes.
Errors	Rows the CRM rejected.
Skipped	Rows that matched a skip rule, were held by a gate, or were filtered out.

Skipped is not failed. A row skipped because your match rule said skip on match, or because a gate held it back, did exactly what you asked. Only the Errors tab is a problem.

Click a row

Any row opens an inspector showing what was actually sent and what came back — the payload per module, the record it matched if it matched one, and the CRM’s own error message if it failed.

That error message is the CRM’s, not ours. When a record is rejected for a reason Sloose could not have known — a validation rule, a workflow, a required field on a layout — this is where you see it in its own words.

The run report

The report gives you three things:

• A summary digest you can copy into a ticket or an email: counts, modules, what the rules did.
• The chronological log, every step in order.
• The raw results, as JSON, downloadable — every row, its payloads, its outcome.

Download the raw results when you need to reconcile against something else, or keep a record outside Sloose of exactly what a run did.

Failures, and what to do with them

Some rows failing while others succeed is a normal outcome, not a broken run.

The shape that works:

1. Filter to Errors and read a few. They usually have one or two causes, not twenty.
2. Fix the cause — a value in the grid, a mapping, a value map.
3. Retry n failed re-runs only those rows.

Rows that succeeded are not touched by a retry.

If the failures are all the same message, the fix is one mapping. If they are all different, the file is probably the problem rather than the mapping.

Run history

Every run — dry or real — is recorded against your org: who started it, when, how many rows, what happened, which modules it touched.

Retention depends on your plan:

Plan	History kept
Free	7 days
Team	30 days
Business	365 days
Enterprise	365 days

History is retired automatically once it is older than that. It is a log, so an old org with an empty list is expected rather than a fault.

What the history does and does not hold

It holds what happened: counts, outcomes, modules, timings, the error message where a run failed.

It does not hold your data. The rows are not copied to our servers, and the history cannot be used to reconstruct the file you imported. If you need that, download the raw results while the run is in front of you, or keep the file.

Saving what worked

If this import is something you will do again, Save it as a project. The mappings, match rules and value maps come back next month and you only bring a new file.

That is the difference between an import taking twenty minutes the first time and two minutes every time after. See Save and reuse a project.