Skip to content

Troubleshooting field guide

Use this guide to choose the next question. It is a triage framework, not a list of verified fixes for every IFS release.

Record the time and error. Confirm the intended environment and follow your organization’s identity-support process. Do not share a password or borrow another person’s session. See access troubleshooting.

Compare filters, business context, environment, and record identity. If the difference persists, ask an authorized administrator to investigate effective access. Avoid adding broad grants to test a guess.

Check whether the standard or configured value exists, how it is exposed, which configuration context applies, and what the role may read. Verify the actual dependencies in the environment. See configuration packages.

Capture its identifier and timeline. Distinguish waiting, execution, failure, and completed work with missing output. Establish whether a retry can duplicate effects. See background-job evidence.

Observation Question to investigate
Authentication error Is the configured authentication valid for this endpoint?
Forbidden operation Does the caller have the required access for this action?
Resource not found Is the environment, service, entity, and key correct?
Validation error Does the input meet the documented contract?
Timeout Is the outcome unknown, and how can it be reconciled safely?

Read the actual status and sanitized response body together; a status alone is not a complete diagnosis. See API discovery and reliability.

Align the population, parameters, timestamp, role, currency, and unit. Compare record identifiers before aggregating values. See reconcile results.

Use the support-handover worksheet. Explain the expected behavior, actual behavior, impact, and smallest reproduction.