# Messages and notices A–Z Every notice, chip, banner and dialog text Atlas can show, apart from the problems in the Problems dock (those are in {doc}`/reference/problems`). Find a message by its first word, or search this page for a few words of it. Parts in angle brackets (``, ``) stand for what Atlas fills in. Each entry says where the message appears, what it means and what to do about it. :::{note} **Where error texts come from.** Many errors show the explanation the backend or the engine gave. Only when there is none does Atlas show its own short text ("Save failed", "Upload failed.", "Could not push"). If the text you see isn't on this page, it is most likely the engine's own message: read it for the cause, and see {doc}`/offer/support` if it doesn't help. ::: :::{note} A few failures show no message at all. The Engine state page shows its welcome screen ("There's nothing here yet") both when the engine is empty and when Atlas couldn't read the engine's state; the Terminology page shows "No ConceptMaps yet." also when it couldn't list them. If you expected content, reload the page and check that the engine is reachable. ::: [Numbers and names](#messages-other) · [A](#messages-a) · [B](#messages-b) · [C](#messages-c) · [D](#messages-d) · [E](#messages-e) · [F](#messages-f) · [G](#messages-g) · [H](#messages-h) · [I](#messages-i) · [J](#messages-j) · [K](#messages-k) · [L](#messages-l) · [M](#messages-m) · [N](#messages-n) · [O](#messages-o) · [P](#messages-p) · [R](#messages-r) · [S](#messages-s) · [T](#messages-t) · [U](#messages-u) · [V](#messages-v) · [W](#messages-w) · [Y](#messages-y) (messages-other)= ## Starting with a number or a name ### \ has \ commits the engine hasn't pulled yet. **Where:** **Versioning** → Remote, and the versioning badge tooltip. After a refused **Push** it reads "\ has commits the engine hasn't pulled yet. Pull first, then push." with a **Pull…** button. Others pushed to the branch. A push never takes their changes into the engine, so it waits until you have pulled them. **What to do:** Click **Pull…** ({doc}`/ship/push-pull`). ### \ has no commits (never connected, or deleted). Connect the engine to it to write its state, then push. **Where:** **Versioning** → Remote (amber), after **Push** (code `connect-required`), with a link to the **Git remote settings**. The branch is empty: the engine was never connected to it, or it was deleted. A push only adds the unpushed changes, so it would leave out the rest of the engine's state. **What to do:** Open the **Git remote settings** and click **Connect** ({doc}`/ship/git-remote`), then push. ### \ no longer contains the engine's last push: its history was rewritten (e.g. force-pushed). **Where:** **Versioning** → Remote (amber). After a refused **Push** it ends with "Pull first, then push." and a **Pull…** button. The branch was rewritten after Atlas's last push. The engine can't tell which of its changes are new there, so it doesn't push until it has pulled. **What to do:** Pull to compare everything, then decide which side wins. ### “\” comes from the core model \; this extension doesn't override it. **Where:** Engine state, mapping detail of an extension model, with **Open \**. The mapping you picked belongs to the model the extension extends. **What to do:** Click **Open \** to edit it there. ### \ maps \, not \. **Where:** Editing sheet, under **Slot archetype**, with **Wrap in a reference to \**. The slotted model maps another FHIR resource than the one in scope at this mapping, so the engine skips the slot ({ref}`problem-slot-resource-mismatch`). **What to do:** Click **Wrap in a reference to \**; see {doc}`/map/connect-models`. ### \ change(s) not pushed — the release only contains pushed changes. **Where:** Release wizard check (amber), with **Push now**. Unpushed changes won't be in the release. **What to do:** Click **Push now** ({doc}`/ship/release`). ### \ error(s), \ warning(s) in the mappings. **Where:** Release wizard check. The template has problems ({doc}`/reference/problems`). **What to do:** Fix them in the Workspace before releasing, or release knowingly. (msg-profiles-not-loaded)= ### \ profile(s) not loaded **Where:** Next to the validation chip (amber link). The produced FHIR claims profiles whose IG packages aren't loaded, so it was validated without them (tooltip "Validated without \ (not loaded). Upload the package that defines it."). **What to do:** Click it to go to **FHIR packages** and add the package ({doc}`/codes-and-profiles/fhir-packages`). (msg-upload-result)= ### \ uploaded · \ skipped · \ failed **Where:** Engine state (and Terminology), after an upload, with a row per file. The result per file: green check uploaded, amber skipped (not a supported or recognisable file, or unchanged), red failed (with the reason). **What to do:** Read the failed rows (below) and fix those files. ### \#\ not found in \ (\) **Where:** **FHIR packages**, fetch. The registry has no package with that id and version. **What to do:** Check the spelling and version (`id#version`). ### \: packages are limited to 15 MB **Where:** **FHIR packages** upload and the create-model wizard, under the listed files (red). The package file is larger than 15 MB; **Upload** stays disabled. The same place says `: files are limited to 60 MB` for any larger file and `: not a .tgz, .json or .zip` for a file of another type. **What to do:** Leave the file out (the cross next to it). Fetch a large package by `id#version` from the registry instead. ### \: \ **Where:** **FHIR packages** upload and the create-model wizard (red). The file named couldn't be stored, so nothing of the upload was. The reason follows the colon, for example `Not a FHIR npm package (.tgz with package/package.json): …`. **What to do:** Leave the file out or fix it, then upload again; the files stay listed. The reasons are explained in {doc}`/codes-and-profiles/fhir-packages`. ### '\' is no package name: use letters, digits, '.', '-' and '_', for example local.my-profiles **Where:** **FHIR packages** upload and the create-model wizard, under the package name (red). The package name for the loose resources has other characters, or starts with `.`, `-` or `_`. **What to do:** Change the name, or clear it to let Atlas name the package. (msg-slot-placement)= ### \ has no model to hold the slot — choose a start / map it first **Where:** Slot placement list (add-mapping dialogs, wizard), next to a greyed occurrence. That place in the template sits in an archetype no model maps yet, so there is no model to put the slot mapping in. **What to do:** Pick another occurrence, choose **Don't slot it now**, or first map the enclosing archetype (or choose the start). (msg-slot-mapped-inline)= ### \ already maps elements inside \ — a model slotted in would map them twice **Where:** Slot placement list (add-mapping dialogs, wizard), next to a greyed occurrence. The enclosing model maps elements of this archetype occurrence itself (inline, through its own paths). A model slotted in there would map the same elements a second time. A mapping that only leads into a slot there (every branch below it ends in a **Slot archetype**, as in a reference + slot) doesn't count. The coverage tree offers no **+ Slot** on such an occurrence for the same reason. **What to do:** Pick another occurrence or choose **Don't slot it now**. To give the occurrence a model of its own, first remove the inline mappings from the enclosing model. ### \ (not found) **Where:** ConceptMap list in the Terminology row. The mapping names a ConceptMap the engine doesn't have. **What to do:** Pick an existing one or upload it ({doc}`/codes-and-profiles/conceptmaps`). (messages-a)= ## A ### A model named '\' already exists **Where:** Create-model wizard. Model names are unique in the engine. **What to do:** Pick another name. ### A version like 1.2.0 **Where:** Release wizard, version field (red). The version isn't in the `major.minor.patch` form. ### Added \#\; its profiles are still loading or it has none for FHIR \. **Where:** Create-model wizard. The package was added, but no profile of the chosen FHIR version is available yet. **What to do:** Wait and look again, or check the package's FHIR version. ### Adding \ to this context… **Where:** Editing sheet, under **Slot archetype**. You picked a model from another template; Atlas is adding it to this one. ### Already up to date: \ has nothing the engine hasn't pushed or pulled. **Where:** **Pull from the remote** dialog (green). Nothing to pull. ### Another mapping here is also named “\”. **Where:** Note in the move or duplicate toast. The mapping now has a sibling with the same name ({ref}`mapping-name-duplicate \`). **What to do:** Rename one of them. ### Another versioning operation is running. Try again in a moment. **Where:** Versioning actions (code `busy`). A push, pull or other operation is in progress. **What to do:** Wait and try again. ### Applied all at once: if anything can't be imported, nothing is, unless you import despite the errors. **Where:** Engine state, upload preview. The engine imports the whole upload as one change. **What to do:** Review the plan, then click **Apply**. If the plan has errors, see {ref}`msg-import-despite-errors`. ### Archive contained no supported files **Where:** Upload result row for a ZIP (skipped). The ZIP holds nothing Atlas can import. ### Asking the engine about versioning… **Where:** **Versioning** and **Git remote** pages. Atlas checks whether the engine versions mappings. ### Auto-save is off — edits stay local and the openEHR & FHIR panes go stale until … > Auto-save is off — edits stay local and the openEHR & FHIR panes go stale until you click Save (or press Ctrl+S). **Where:** Under the model editor, next to **Auto save**. Auto-save is off: edits stay in your browser until you save, and the example panes show the last saved state. **What to do:** Click **Save** in the top bar or press {kbd}`Ctrl+S`. ### Auto-save is on — edits save automatically **Where:** Workspace top bar, a short hint after {kbd}`Ctrl+S`. You pressed {kbd}`Ctrl+S` while auto-save is on; any pending edit is saved now. ### Auto-saves to the engine shortly after you stop editing, then re-runs. **Where:** Under the model editor, next to **Auto save**. Auto-save is on: each pause in editing saves the model and converts the example again. **What to do:** Untick **Auto save** to collect edits and save them yourself. Auto-save is on again at each visit to the Workspace. ### Available on dedicated instances only **Where:** **Integrations** and **Multitenancy** pages. These capabilities need a dedicated openFHIR instance and aren't available on a shared one. **What to do:** Use **Contact us** on the page ({doc}`/offer/dedicated-instances`). (messages-b)= ## B ### Building the FHIR profile set failed: \ **Where:** Path suggestions, checks or validation, while packages load (code `warming`). Atlas couldn't read the loaded packages. **What to do:** Check the packages on **FHIR packages** for a **not loaded** chip. (messages-c)= ## C ### Checking what the upload changes… **Where:** Engine state, upload panel. Atlas asks the engine for a preview of what the upload would change. ### Choose a start archetype for this template **Where:** Template overview, where the start model would be. The template's context mapper has no start yet, so nothing is mapped. **What to do:** Click it and pick the archetype where conversion begins ({doc}`/map/start-mapping`). ### Closed without merging: the engine still has these changes, \ doesn't (\ artefact(s)). **Where:** **Versioning** → Reviews (amber), with **Revert the engine to \**. The review was closed, so the branch lacks changes the engine still has. **What to do:** Resubmit, or revert the engine to the branch ({doc}`/ship/reviews`). ### Connect or pull first: the engine hasn't synced with this branch. **Where:** **Versioning**: a push from a dialog (**Checkpoint and push**, the release wizard's **Push now**), when the engine gave no explanation of its own (code `pull-required`, remote state `untracked`). The engine never pushed to or pulled from the branch: the repository was never connected, or the repository URL or branch setting changed. **What to do:** Usually open the **Git remote settings** and click **Connect** ({doc}`/ship/git-remote`). Pull only if the repository should replace the engine: a pull plans to delete every engine artefact the repository lacks. ### Context not found for template: \