Skip to main content

Fixing a save error in a learning journey

Why you might get an error when saving a change in a learning journey — almost always an unsupported character or an over-long field carried in by a default, duplication, or translation — and how to find and fix it.

If you get an error when you try to save a change — to a micro-training, an activity, or any other part of a learning journey — the cause is almost always the same: one of the fields holds either a character Knowly can't store or more text than it can fit. Once you know where to look, it's usually a quick fix.


What's usually behind it

Most save errors come down to one of two things, often in a field you didn't type into yourself:

  • An unsupported character — a symbol pasted in from another program, an emoji, or a stray invisible character can block the save.

  • A field that's too long — there's more text in it than the field allows.

These tend to arrive without you noticing. The usual sources:

  • A default — a long learning journey name gets filled into other fields automatically and pushes them over the limit.

  • Duplication — copying a journey or activity brings along whatever was in the original, including an over-long or odd value.

  • Translation — a translated journey can end up with longer text, or characters, that the original didn't have.


How to find and fix it

Go through the activity you were editing and check the longest or most recently changed fields first:

  • shorten anything that looks unusually long — titles, headings, button text, sender names

  • if you duplicated or translated the journey, look at the fields that came from the original, since that's where an odd value tends to hide

  • if your learning journey name is very long, try shortening it and then save again

Save after each change so you can tell which field was the problem.


If it still won't save

If none of that clears the error, it may be a different issue — for example a very large micro-training that takes too long to save. Contact [email protected] and include the name of the learning journey and the activity you were editing, so we can find it from our side.

Did this answer your question?