Troubleshooting
At a glance
- Most warnings just mean a required step was skipped — read the message, it names the missing piece.
- A few errors mean the link you arrived on is broken, not something you did.
- If something fails outright (parsing, rendering, saving, deploying), that's a distinct message from a plain warning — know the difference when reporting an issue.
MorphMapper tells you when something's wrong with a short message rather than leaving you to guess. This page groups the ones you're most likely to run into, in plain terms.
When you first arrive
| Message | Meaning | Fix |
|---|---|---|
| "No userId provided in the URL" / "No JWT Token provided in the URL" | The link you used to get into MorphMapper is missing something it needs. | See Getting started; go back to wherever you got the link and open it again rather than trying to fix the URL yourself. |
| "Invalid domains: ..." | Your organization is configured with access to a domain that doesn't actually exist for it. | Not fixable from your side; an admin needs to correct the configuration. |
During setup
| Message | Meaning | Fix |
|---|---|---|
| "Please select a domain / template / file" | You tried to continue without picking one. Not an error, just a reminder. | Pick one and continue. |
| "message.error.required" | Shown under a field in the create-template form (Name, Input Source, Template Variant, Schema, Category, or Priority) that's still empty when you click Create. It's a raw, untranslated label rather than a friendly sentence. | Read it as "this field is required" and fill in whatever it's pointing at. |
| "Failed to parse the selected file" | The file you uploaded couldn't be read as the type your template expects. | Double check it's actually the right format (a .csv selected for an XML template won't parse, for instance). |
| "Failed to load recent files" / "Failed to load the selected recent file" / "Failed to download the selected recent file" | A problem reaching a previously used file, distinct from a problem with a file you're uploading fresh. | Try again, or upload the file directly instead of via Recent Files. |
While working on a template
| Message | Meaning | Fix |
|---|---|---|
| "Please select a type" / "Please enter a name" / "Please select a map type" | You clicked Create in the add-entry dialog without finishing it: no type chosen, no name typed, or (for a group entry) no choice yet for how its children combine. | Fill in the missing piece and create it again. |
| "Failed to render template" | Something in your current mapping can't be turned into output right now. | Check the graph or code for the entry you were last editing; this is usually the first place to look. |
| "Failed to save template" | Your save didn't go through. Your work isn't lost from the screen, but it also isn't backed up yet. | Try saving again before navigating away. |
| "Failed to deploy template" | Deployment didn't complete. Deploying is the step with real consequences (see Testing, saving, and deploying). | Confirm your template still tests correctly before trying again. |
| "common.search" | The placeholder text in the node picker's search box in the graph editor. Like message.error.required above, it's a raw, untranslated label rather than real placeholder text. | Cosmetic only; the search box works normally, so ignore it. |
Categories and templates
| Message | Meaning | Fix |
|---|---|---|
| "Category name already exists" | Category names must be unique (and you can't reuse "default"). | Pick a different name. |
| "Category must be empty to delete" | A category can't be deleted while it still contains templates. | Move or delete every template in it first. |
| "Could not create template" | Shown whether you were creating a new template or duplicating an existing one; duplicating reuses the same creation step under the hood, so it fails the same way with the same message. | Check that every required field in the form has a valid value, particularly the schema selection, which depends on picking a type and variant first. |
Still stuck?
If a message here doesn't match what you're seeing, or the suggested fix doesn't help, use the chat assistant's Bug report starting point — it's the fastest way to get it in front of someone who can actually look into it.