Skip to main content

Monitor and Troubleshoot

Administration & operations

Find the failed run, locate where the workflow stopped, and verify one safe record before returning to scheduled automation.

Use this guide when a job reports an error, a scheduled task does not run, or an expected account or access change is missing. Begin with the result from the affected run so you can focus on the part that actually failed.

At a glanceDirect link to At a glance

Start with the affected job or scheduled task result. Check whether NIM selected the record, then follow its data through collection, relations, filters, and mappings or roles. If the target rejected the operation, inspect its permissions and the matching log message before retrying a single record.

Start with the runDirect link to Start with the run

01 · Job resultWhat did NIM attempt?

Check the latest run for the affected mapping or role. Did it select records, pass validation, and attempt a target change?

Review job results →02 · Scheduled taskDid the automation run?

Confirm the task started and completed. Compare its time and status with the job result.

Review task results →03 · LogsWhat error explains the result?

Match the run time and context to the General or Script log. Read the first meaningful warning or error.

Review logs →
Save the evidence before changing anything

Record the run time, affected record, job or task result, and relevant log message. This makes the next check more precise and gives you a useful starting point if you need help.

Find the failing stageDirect link to Find the failing stage

Use the result from the affected run to follow the first answer that is No. Each row leads to the next question when the answer is Yes.

  1. 1
    Did the scheduled task start?

    No → Check the schedule and task configuration.

    Yes ↓ Open the job result.

  2. 2
    Did the job select the expected record?

    No → Check collection, relations, and the filter.

    Yes ↓ Inspect the target operation.

  3. 3
    Did the target accept the change?

    No → Check the mapping and values, then target permissions.

    Yes → Confirm the target state and normal schedule.

Troubleshoot provisioning failuresDirect link to Troubleshoot provisioning failures

When NIM does not create, update, disable, or remove the expected record, follow the checks that match the failed stage. Start with the selected record and only retry a broader job after a safe single-record test succeeds.

1

Confirm current data

Check that the relevant system collection completed. In the Vault, find the source record, any existing target record, and the required attributes.

If data is missing: fix the connection, collected tables or columns, or collection error first.

2

Check record relations

If more than one system supplies data, inspect the inter-system relation. Confirm that it matches the selected source record to the correct target record.

If the match is wrong: correct the relation before changing the filter or mapping.

3

Preview the filter

Open the filter used by the mapping or role. The selected record should appear with every column needed for the target operation.

  • Missing record: check the start table, conditions, collection, and relations.
  • Missing values: check columns, lookups, generators, and source data.
  • Extra records: narrow the criteria before another run.
4

Validate the operation

Check the mapping or role, target system, operation, and required values. Resolve validation errors.

Then confirm: the mapping or role is included in the job being tested.

5

Check target access

If NIM selected the record but the target rejected the change, check the connector account, certificate, consent, API permissions, or delegated rights for that exact operation and scope.

Use: the integration's connection guide and connector permissions guidance. Run a connection test where available.

6

Verify one safe record

Collect changed data again, preview the filter, then test one record through the job. Review its new result and confirm the target state.

Only after it succeeds: return the job to its normal sync task schedule.

Jump in by symptomDirect link to Jump in by symptom

No records changeCheck the job contents and filter preview, then trace collection and relations.Start with filter output →The wrong records changeStop broad runs and check filter criteria and record matching.Inspect selection →A selected record has no target changeCheck the mapping or role operation, then the target connection.Inspect the operation →The target returns an errorCompare the job result with required values and connector permissions.Inspect target access →A correction has no effectCheck validation and whether the latest data or configuration has loaded.Open general troubleshooting →

Troubleshoot by areaDirect link to Troubleshoot by area

If the provisioning path does not match the issue, choose the guide for the affected part of NIM.

Systems & configurationNIM troubleshooting

Diagnose collection, filter, relation, validation, and service problems.

Open NIM troubleshooting →Access modelRole troubleshooting

Find why a person received missing or unexpected role-based access.

Open role troubleshooting →Self servicePassword-reset troubleshooting

Check reset flows, enrollment, notifications, and common log errors.

Open password-reset troubleshooting →Self serviceOnboarding troubleshooting

Diagnose onboarding URL, verification, session, and record-status failures.

Open onboarding troubleshooting →
Last updated on