Skip to main content

Troubleshooting guide

Welcome to the centre for solving operational problems in the Skool.Cool admin portal. This guide gathers the situations school managers and coordinators meet most often in the field — with the cause confirmed from the system, and a practical fix for each.


When do you use this guide?​

  • When an error appears during daily work (approving, paying, scheduling, importing) and you do not know why.
  • When a user (a coordinator, a trainer, a guardian) reports a problem that needs a quick diagnosis.
  • Before escalating to support — many cases have a direct fix here.

An index of quick fixes​

1. Cannot sign in, or the temporary password​

  • The symptoms: the user cannot sign in and meets a repeating error, or is caught in a redirect loop to the change-password screen.
  • The cause: the session has expired, or the user is signing in for the first time with a one-time temporary password and has not finished setting a new one meeting the strength requirements, or the email or password is wrong, or the account is locked for 15 minutes after 5 wrong attempts in a row (on the sign-in screen, or in Current password on the change-password screen).
  • The fix:
    1. Check the email is correct and has no spaces before or after it.
    2. If this is a first sign-in with a temporary password, the system takes you to the Change password screen with a banner saying you signed in with a temporary password. Set a password meeting the requirements: at least 8 characters with an upper- and lower-case letter, a number and a symbol.
    3. If the user has forgotten their password or it no longer works, only a SystemAdmin — the Skool.Cool support team — can reset it; Reset password does not appear for a school manager or any other admin. So a colleague who can sign in (their school manager, for example) asks the support team through Help or request, and a new one-time password is created and handed to the user to sign in with and then change. (There is no separate "unlock account" button — resetting is the supported path: if the account is locked after 5 wrong attempts, a reset lifts the lock, so the new password works at once. Without a reset, wait 15 minutes from the moment it locked, then sign in; attempts during the lock do not extend it.)

See: Signing in and verification · Managing school admins.

2. The activity is not visible to parents​

  • The symptoms: a guardian looks for the new activity in their app and cannot find it to register.
  • The cause: the activity has not been published to parents yet — its status is Closed (new activities start closed until published), or the allowed-for-parent option is off, or the child's age range does not match the ranges set for the activity, or the school itself is Hidden from marketplace or Suspended.
  • The fix:
    1. Open the Activities screen and check the activity's status. If it shows Closed, open the activity's panel and choose Publish to parents — the activity moves to Open.
    2. Check that Allowed for parent is turned on, in the Schedule step of the edit-activity wizard.
    3. Check the child's date of birth matches the age ranges assigned to the activity.
    4. In Platform → Schools, check the school's card: a Hidden from marketplace badge means its activities do not appear when parents browse, though they still work through their direct links and the school portal; Suspended means the school is gone from parents entirely. Changing either is done by the Skool.Cool team.

See: The activity lifecycle and its states · Create a new activity · Your school in the public marketplace, and suspension.

3. Cannot approve a registration request​

  • The symptoms: the coordinator presses Approve, a red error appears, and the student's status does not change.
  • The cause: the activity has reached its maximum Capacity, or the activity has been closed or ended.
  • The fix:
    1. Check how many students are currently accepted against the capacity.
    2. If the activity is full, either raise the capacity from the edit-activity screen (from 20 to 25, say), or press Add to waiting list from the row's more-actions menu until a seat frees up.
    3. And if you do raise the capacity, open the waiting list straight afterwards and admit whoever is due. Raising capacity opens the seats without an alert reaching anyone — the alert is for cancellations and withdrawals alone, and the system promotes nobody automatically.

See: Approving a registration request · The waiting list · Fees and capacity.

4. Cannot edit the session schedule​

  • The symptoms: an administrator tries to change the session days or times and the fields appear greyed out and locked.
  • The cause: the system locks schedule editing automatically when the activity has active registrations (to protect the families registered), for anyone without the permission to edit the schedule after registrations exist. In addition, any session with recorded attendance stays locked for everyone, because it has become a historical record.
  • The fix:
    • If the change is essential, it is made by the school's owner or a system administrator (those with the permission to edit the schedule despite registrations) from the activity's schedule screen.
    • Sessions with recorded attendance cannot be changed at all — they remain a historical record; limit yourself to the coming sessions whose attendance has not been taken yet.

See: Scheduling weekly sessions.

5. Common Excel import failures​

  • The symptoms: uploading the parents or students file fails with a general red error message.
  • The cause: cells that fail validation (an unrecognisable date, an invalid mobile number, an empty mandatory field), a duplicate within the file itself, or a child row whose guardian's mobile number is neither in the file nor in the system.
  • The fix:
    1. Download the error report with Download error file — it explains the reason for each row separately, and is the fastest route to a diagnosis.
    2. Correct the rows it lists and upload again, or carry on with the good ones alone using Import valid rows only.
    3. If you see a message that no parent account exists with a given mobile number, there is no guardian account with that number. Check the cell first; if the number is right, ask the guardian to create their account in the parents app, then import the row again. The import does not create guardian accounts — see Importing students and their guardians.
The column order and names do not matter

The file no longer needs a fixed order or literal heading names; the Map columns step links your file's columns to Skool.Cool's fields and lets you correct any mapping by hand. The template from Download template is a convenience, not a requirement.

See: Importing parents from Excel · Importing students from Excel · Reference: Excel columns.

6. An online payment is stuck​

  • The symptoms: a guardian paid by card and the money was taken, but their registration's status is still Awaiting payment.
  • The cause: a momentary break in the automatic connection with the payment gateway before the transaction's confirmation reached the system.
  • The fix:
    • Wait, and do not confirm the payment by hand. The platform asks the payment gateway itself and corrects the status automatically, usually within half an hour at most.
    • The status may pass momentarily through User paid and then settle on Paid by itself; nothing is required from you. And if it stops there, contact support — Confirm payment on it returns that the payment was already confirmed.
    • If it is still Awaiting payment after that, contact support. Do not use Confirm payment here: it is for cash actually received, the reference number from the guardian cannot be verified, and the operation is either refused or cancels their payment link and records cash the school never received.

See: Handling a failed payment · Confirming a cash payment.

7. Attendance marking will not save​

  • The symptoms: the red Save failed — retry state appears at the top of the session attendance screen, and autosave stops.
  • The cause: a temporary break in the trainer's Wi-Fi or internet while they are out in the field.
  • The fix:
    1. Do not close the browser tab, so the marking in progress is not lost — the system warns you before leaving the page if there are unsaved changes.
    2. Carry on marking students normally; the changes are gathered temporarily until the connection returns.
    3. As soon as the internet is back, press the Save failed — retry text itself to save the accumulated changes in one go.

See: Autosave and working offline · Taking session attendance.

8. The registrations or attendance list looks empty or incomplete​

  • The symptoms: you open the Registrations or Attendance screen and the registrations you expected are not shown, or only one activity's data appears without the rest.
  • The cause: the activity filter in the top bar is set to a single activity instead of All activities, narrowing the registrations and attendance to it and hiding the rest. It may also be that the wrong school is selected in the school switcher.
  • The fix:
    1. Open the activity filter in the top bar and set it back to All activities to show every registration and attendance record.
    2. Check the right school is selected in the school switcher at the top of the screen.

See: Navigation and the portal's interface.

9. Groups do not appear to an admin scoped to particular activities​

  • The symptoms: an administrator whose access is limited to particular activities creates a group inside a main activity they do have access to, and then the group does not appear in their lists — even the groups they just created themselves.
  • The cause: the lists used to show only the activities recorded against the account, and creating a new group did not add it to that list automatically. So the group disappeared even though its creator held the very permission. This was a defect in the system rather than an entry error, and no data was ever lost — the groups existed the whole time.
  • The fix: it has been fixed and released. Permission on any main activity now automatically covers every group beneath it, with no manual step. If you were using the portal during the release, refresh the page and sign in again.
  • You do not need to: widen the account's access to school level as a workaround. Leave the limited access as it is — it now works as expected, and widening it grants more access than necessary.

The fix also covers: the activities and archived-activities lists, the waiting list, the queue summary, and the renewal lists. It now covers saving as well: editing the group, choosing its trainers, and working on its registrations, which used to be refused with "Your changes were not saved" even though the group appeared in the lists.

See: Troubleshooting access.

10. A child added by a guardian is not in the school's lists​

  • The symptoms: a guardian insists they added their child, but the child does not appear in the school's directories or lists however often you search. The guardian may think the child is "linked to another account".
  • The cause: adding a child to a guardian's account does not link them to any particular school. A child appears in a school's lists only after a registration on one of its activities is complete, or after being granted membership of it. This is deliberate, to protect children's privacy, and not a fault: a child's profile belongs to the family until it is genuinely linked to a school.
  • The fix:
    1. First check the registration really is complete — in many cases the child is added to the account with no completed registration request.
    2. Ask the guardian to complete the registration on the activity they want; the child appears in your lists as soon as it completes.
    3. If the child should be linked to your school without a registration, open a support request for us to link them.

11. A national ID is refused although it is ten digits​

  • The symptoms: a guardian or an admin tries to correct a child's ID number, and it is refused even though the number entered really is ten digits.
  • The cause: the number of digits is not the only condition. National ID, iqama and border numbers follow a numbering scheme with a check digit: the last digit is calculated from the nine before it. If a single digit is wrong, or swapped with its neighbour, this check fails and the number is refused however correct its length. The check is deliberate: the ID number is what a child's records are matched by, and a wrong number links the child to records that are not theirs.
  • The fix:
    1. Compare the number with the child's official document digit by digit — the national ID, the iqama or the border number.
    2. Look specifically for two neighbouring digits that have been swapped; it is the most common cause of a refusal and the hardest to spot.
    3. If the number currently saved on the child's file is accepted by the system, it is most likely the right one and the mistake is in the new number. Check both before changing anything.
    4. If you have checked the document and the refusal remains, open a support request and say so explicitly — and do not enter a substitute number just to get it accepted.
Do not change a child's national ID to get around a refusal

The national ID is what a child is matched by across the records, and changing it can cut them off from their earlier records and make it hard to undo. Whenever an action is refused and the reason is not clear, open a support request rather than editing the ID.

12. A sign-in email or phone change for an admin or trainer is refused​

  • Symptoms: when you save an admin's or trainer's details, a message says that changing the sign-in email or phone number is outside your access, while a change to the name or city saves normally.
  • Cause: a person has one sign-in account across every school and every role they hold. If the account is linked to another school you do not administer, or to another role of the same person, changing its sign-in email or phone from your school would change how they sign in everywhere. So this change is limited to an account that lies entirely within your access. This is intended, to protect users' accounts, not a fault.
  • What to do:
    1. Put the email and phone back to their current values and save your other changes; they save as usual.
    2. If the email or phone really must change, ask a system administrator.
  • Note: whenever an allowed change is made to a sign-in email or phone, the account holder is asked to sign in again, and the change is recorded in the audit log.

13. An "unexpected error" message and its reference​

  • Symptoms: when you save something or carry out an action — approving a registration, saving the answers to registration questions, saving an activity — a red message says "An unexpected error occurred. Please try again, and quote the reference below if it keeps happening.", and under it a line Reference: followed by a code of Latin letters and digits.
  • Cause: the system could not complete the request because of a fault on its side, not because of what you entered. Every fault of this kind is logged, and the reference is what leads the support team to the record of your request in particular.
  • What to do:
    1. Try again once; many of these are momentary.
    2. If the message comes back, copy the reference — one click on it selects all of it — or take a screenshot, then send it in a Something is broken request from the Help button in the top bar, with what you were doing and roughly when.
    3. For payments and refunds, do not repeat the action again and again: open the registration and check its status first, and if it is still unclear, send the reference and wait for support's reply.

See: Asking for help from inside the portal.

14. An "action could not be completed" message​

  • Symptoms: when you carry out an action, a red message says "This action could not be completed. Reload the page and try again; if it keeps happening, contact support."
  • Cause: the system refused the action for a reason it records but the message does not show — the record may have changed since you opened the page, for example.
  • What to do:
    1. Reload the page so it shows the record as it is now, then carry out the action once more.
    2. If the message comes back, send a Something is broken request from the Help button in the top bar, with what you were doing, the record you were working on and roughly when; those details are what lead the support team to the recorded reason.
    3. For payments and refunds, open the registration and check its status before you repeat the action.

See: Asking for help from inside the portal.​

A permissions problem? It has its own guide

If the problem is that a member of staff cannot see a button or a screen, or that a change to the roles has had no effect, start from Troubleshooting access — it has a four-step diagnosis and a full symptom table.


Frequently asked questions​

Why is the activity I created not visible to parents? Most likely because it is still Closed and has not been published. Open the activity's panel and choose Publish to parents to move it to Open, and check that the allowed-for-parent option is on and the age range matches. More detail in The activity lifecycle.

I forgot my password and cannot get in — what do I do? Only a SystemAdmin — the Skool.Cool support team — can reset a password; Reset password does not appear for a school manager. Ask a colleague who can sign in (your school manager, for example) to send the request to the support team through Help or request, and a new one-time password is created for you to sign in with and then change. The details are in Resetting an admin's password.

Why are the fields locked so I cannot edit the session schedule? Because the activity has active registrations (the schedule locks to protect the families), or because the session has recorded attendance and has become a locked historical record for everyone. The school's owner or a system administrator can edit the coming sessions only. See Scheduling weekly sessions.

The guardian paid by card and the status is still "Awaiting payment" — how do I record the payment? Do not record it by hand. The platform re-checks the payment gateway automatically and corrects the status to Paid itself, usually within half an hour — an online payment is never confirmed by hand. If the status is unchanged after that, contact support. The full steps are in Handling a failed payment.

One of my admins is scoped to particular activities, created a group, and it no longer appears to them. Why? This was a system defect and it has been fixed and released: holding permission on a main activity now automatically covers all its groups. Refresh the page and sign in again. There is no need to widen their access to school level. The details are in section 9 above.

A guardian says they added their child and we cannot see them in our lists — where is the problem? Most likely there is none: adding a child to a guardian's account does not link them to a school. The child appears for you once their registration on an activity is complete, or once they are granted membership. Check first that the registration really did complete. The details are in section 10 above.

The ID number I enter is ten digits and the system refuses it — what is going on? The number of digits is not the only condition: the last digit of national ID, iqama and border numbers is calculated from the nine before it, so a single swapped digit fails the check even when the length is right. Compare the number with the official document digit by digit, and do not enter a substitute number just to get it accepted. Details in section 11 above.

Where do I find the exact reason an Excel import failed? Download the error report with Download error file after the attempt — it explains the error for each row separately. And you do not need a fixed column order: the Map columns step takes care of that. See Reference: Excel columns.