Direct answer
Dataspell does not publish a specific user-facing error code or a guaranteed "Dictionary Load Failed" dialog for an inaccessible dictionary asset. The expected indicator is an IDE log entry from the bundled spell-checker or dictionary plugin, sometimes accompanied by a non-modal notification depending on the plugin and platform version. A missing or corrupted dictionary does not block IDE startup or code execution; it typically affects only spell-checking or validation features.
Dataspell is not expected to log "Dictionary Load Success" at initialization when the asset is absent. Success messages, when they exist, appear only after a successful load, and some integrations log nothing on success. The failure is typically logged at warning or error severity in idea.log, not critical. Critical severity would require a hard-required validation component to fail, which is version- and integration-specific.
Confirmed facts versus likely explanation
| Item | Status |
| Public Dataspell error code for missing dictionary | Not confirmed; no stable API |
| Observable indicator | Likely idea.log entry from spell-checker or dictionary plugin |
| Success log when asset absent | Not expected |
| Failure severity | Typically warning or error; critical only if hard-required |
Verification steps for this case
- Record the Dataspell version and the exact dictionary resource path or provider from the IDE settings.
- Back up the configured dictionary file, then temporarily rename it or point the setting to a missing or corrupt
.dic/.aff or word-list file.
- Restart Dataspell or invalidate caches, then trigger the validation or spell-check action that uses the dictionary.
- Open Help | Show Log in Explorer/Finder and search
idea.log for dictionary, Hunspell, spellchecker, and the plugin name. Check whether a failure entry appears and whether any success message is logged.
- Restore the valid asset and repeat to confirm the present-versus-absent difference.
Missing diagnostic detail
Because behavior depends on the Dataspell/IntelliJ platform version and dictionary provider, provide the Dataspell version and configured dictionary path before applying version-specific log filters.
Assumptions and uncertainty
- The condition is local resource accessibility, not network resolution, per the stated constraints.
- Plugin-specific log text and severity can change between releases and are not a stable Dataspell API.
- This draft is conservative and intended for human review until the version and provider are confirmed.