That photo could not be read on our side. Nothing was charged. Please try it once more.
That photo could not be read on our side. Nothing was charged. Please try it once more.
Developer guidelines
Writing and errors
Every error says three things
What happened. In plain words: “That photo could not be read on our side.”
What to do next. One clear step: “Please try it once more.” or “Top up and try again.”
Charged or not. Always say it: “Nothing was charged.”
Most of the sentences Switch sends back for a failed generation already read this way; when one does, you can show it as it is. Keep the error code for your logs.
Leave out
Codes and field names. No status numbers, error codes, field names or server names on screen.
Raw engine text. No stack traces and no messages copied from the engine behind Switch.
Statuses are words
A status is a coloured word in a sentence (“Ready. Your video is in your library.”), never a small box or pill. Money and token amounts are always written in numerals.
Do and don’t
You do not have enough tokens for this. Top up and try again. Nothing was charged.
You do not have enough tokens for this. Top up and try again. Nothing was charged.
Do. Say what happened, what next and whether anything was charged.
Error 502: upstream provider timeout (task_failed)
Error 502: upstream provider timeout (task_failed)
Don’t. Pass on a raw code or the engine’s own text.