Skip to main content

🔧 Understanding and resolving Didask error codes

Encountered an error message on the platform? This guide explains what it means and how to fix it.

Written by Océane

⏱️ The essentials

• All errors follow a category.reason format (e.g. publication.not_found).
• The HTTP code alone is often enough to identify the cause: 401/403 = login or permissions, 404 = deleted content, 400 = invalid input, 429 = too many attempts, 500 = contact support.
• Most errors can be resolved without contacting support. For persistent 500 errors, reach out via the chatbot.


⚡ Quick diagnosis by HTTP code

If you see an HTTP code without further detail, start here:

HTTP code

What it means

First step

401

Not logged in or session expired

Log out and log back in

403

Access denied or account disabled

Check your role and account status

404

Deleted content or incorrect identifier

Check whether the content still exists

400

Invalid input or incorrect format

Check what was submitted

409

Conflict (duplicate or reuse)

See the specific code below

413

File too large

Compress or split the file

429

Too many attempts

Wait 15 to 60 minutes before retrying

500

Server error

Contact support if the error persists


🔐 Authentication & access

The most common errors, most are resolved with a simple re-login or a permissions adjustment.

Code

What it means

What to do

auth.user.not_logged_in (401)

Session expired

Log in again

auth.session_expired (401)

Disconnected due to inactivity

Log in again

auth.not_allowed (403)

Insufficient permissions

Ask an administrator to change your role

auth.invalid_password (401)

Incorrect password

Reset your password

auth.disabled_user (403)

Account disabled

Contact an administrator to reactivate it

auth.rate_limit_exceeded (429)

Too many login attempts

Wait 15 to 60 minutes before retrying

auth.project_not_accessible (403)

Not authorised on this project

Check the project's sharing settings


👤 User accounts

These errors typically appear during sign-up, import, or account management.

Code

What it means

What to do

user.not_found (404)

Incorrect identifier or email

Check the identifier used

user.email_already_exists (400)

Email already in use

Log in with that existing account

user.blacklisted_email_domain (400)

Email domain blocked by the workspace

Contact an administrator to whitelist the domain

user.incorrect_password_pattern (400)

Password too weak

Choose a stronger password

user.password_reuse_not_allowed (409)

Old password reused

Choose a new password


📚 Content - courses, modules, granules

These errors most often occur following deleted content or a missing enrolment.

Code

What it means

What to do

publication.not_found (404)

Publication deleted or incorrect identifier

Check whether the publication still exists

publication.not_allowed (403)

Learner not enrolled

Add the learner to the publication's audience

project.not_found (404)

Project deleted or access not authorised

Check that the project exists and that you have access

project.already_exists (409)

Project name already in use

Choose a different name

topic.not_found / granule.not_found / module.not_found (404)

Deleted content

Refresh the page, the content may have been updated in the meantime

space.not_visible (403)

Training space access missing

Contact an administrator to request access


📎 Files & imports

These errors are almost always fixable without contacting support.

Code

What it means

What to do

file.too_large (413)

File too large

Compress or split the file

file.unsupported_mime_type (400)

Format not accepted

Check the compatible formats and convert if necessary

file.upload_failed (500)

Server-side failure

Retry; contact support if the error persists

file.empty_file (422)

Empty file uploaded

Check the file contents before uploading again


🎓 Learner sessions

Errors that may appear during an active learning session.

Code

What it means

What to do

session_sprint.no_learner_identity (401)

Learner identity could not be resolved

Log out and log back in

take_home_assignment_sprint.already_submitted (403)

Assignment already submitted

Expected behaviour, submission is locked after the first attempt

corrected_assignment_sprint.generation_failed (400)

AI feedback generation failed

Retry; contact support if the error repeats


🔒 Features not enabled

These errors appear when a feature is not included in your contract.

Code

What it means

What to do

workspace.feature.*_not_enabled (403)

Feature not available on your plan

Contact your Didask account manager to find out more


💥 System errors

Code

What it means

What to do

error.unknown (500)

Unexpected server-side error

Contact support via the chatbot with the full context

api.invalid_args (400)

Malformed API request

Check the parameters sent

connector.sync_failed (400–503)

External integration sync failure (Paragon, Ypareo, Cegid)

Contact support, log review required


Keywords: error codes, troubleshooting, HTTP, authentication, access rights, import, learner session, connector, anomaly

Did this answer your question?