Evidence-First Mindtickle Failure Triage

Overview

Classify a failure by boundary, protect learner data, and produce the smallest reversible diagnosis before changing tenant state.

Prerequisites

• An incident owner, affected tenant, time window, population, and business impact
• The last known-good state and recent changes across identity, content, data, and integrations
• Approved access to redacted application and tenant evidence

Tool Discipline

Use Read, Glob, and Grep to inspect local logs and configuration, WebFetch for current official and authorized tenant guidance, and Write or Edit for a sanitized timeline and support packet.

Current Contract

Failures can cross customer identity providers, user sync, tenant roles, subscribed modules, managed connectors, customer adapters, and Mindtickle service boundaries. HTTP status alone does not prove root cause, and public material does not define universal error payloads.