Troubleshoot a blocked workflow
Check context, setup and authority before repeating a payment, import or academic decision.
Start with the saved state and the exact error. Repeating a write without understanding its state can duplicate administrative work or obscure the original failure.
Diagnose by symptom
| Symptom | First checks |
|---|---|
| A page or menu is missing | Correct workspace, effective permission, unit scope, module enabled and subscription entitlement |
| A register is empty | Working session, class, section, live placement and teaching allocation |
| A historical write is refused | Session closed; use the history importer or an authorized reason-bearing reopening |
| A student cannot register | Placement, term and track, window or PIN, fees, standing, prerequisites, carryovers, required courses, load and capacity |
| A result is not visible | Correct child and session; school publication or higher education Senate ratification completed |
| A clearance action is refused | Signing permission, office mapping, unit scope and whether the award is already published |
| A transcript request is unavailable | A valid per-copy fee must be configured, including explicit zero for no payment |
| A payment is still pending | Original reference, amount and currency, gateway recheck and finance review |
| An import has rejected rows | Matching identifiers, dependencies, chosen resource, row report and session state |
| An integration returns 403 | Key’s actual scopes; public read access is separate from internal identity-dependent actions |
Inspect before changing policy
Use Setup for incomplete configuration and the relevant queue for a pending decision. If several sessions are open, check the session shown in the header. If the record is student-specific, verify that student’s own placement and cohort.
A saved role name does not describe the full authority: customized permission bundles and scopes can differ. Ask an administrator to inspect the user’s effective access.
Preserve useful evidence
When contacting the institution or Takadar team, include the page, intended action, session, relevant reference or import batch, exact error and approximate time. Share only the information necessary for the support case. Never send passwords, API secrets or payment-card details.
For a delayed payment, retain the original reference and avoid creating a second credit while the first is being reconciled. For a partial bulk action, read the skip report and correct only the unresolved records. Use the availability guide when a requested step is outside the implemented workflow.