Docs / Help

Troubleshooting

Common problems and how to fix them.

#Problems in the editor

Volley lists problems in the bar under the editor with a line and column. Click one to jump to it.

#Unrecognized line

Unrecognized line: "Client sends the order"

The line is not a statement Volley knows. The usual causes:

• A missing arrow. A message needs an arrow between two lane names: Client -> Shop: sends the order.
• A missing colon after a keyword, such as note or title.
• A stray line after a block ended. A payload or multi-line note ends at the first line that reads as a statement. Text after that is not part of the block. Move it up, or fence the body.
• Prose. Put explanations in a note:, or make them a comment with //.

#"in:" must follow a message

An in: or out: block must come right after a message, or after that message's in: block. It cannot follow a note, a divider or the start of a section. Move it under the message it belongs to.

#Message already has an input

Message 3 already has an input; this one replaces it

A message has at most one in: and one out:. Merge the two bodies, or move one to the reply arrow.

#Section never closed

Section opened here is never closed with "end"

Every if and group needs an end. The problem points at the line that opened the section. Similar messages appear for an else or end with no section open.

#The diagram looks wrong

#A lane appears twice

Lane names must match exactly, including capitals and spaces. Auth Server and Auth server are two lanes. Accept the editor's lane name suggestions to avoid this, or use Rename in the lane menu to merge one into the other.

#A lane has a strange name

If a message has no colon, everything after the arrow becomes the second lane's name. App -> API GET /me makes a lane called API GET /me. Add the colon: App -> API: GET /me.

#A payload ends early or swallows the next lines

An unfenced payload body ends at the first line that reads as a statement. A field named title, order, note, in, out, if, else, end or group closes it. Wrap the body in a fenced block. In the other direction, if the next message is missing its arrow, the payload keeps going; fix the message line.

#A reply is not linked to its request

A dashed arrow answers the latest unanswered solid or bold arrow going the other way between the same two lanes. Check that:

• the reply is dashed (-->), and the request is solid or bold;
• the lanes are the same two, spelled the same way;
• another dashed arrow has not already answered that request.

#The fields table is empty

The inspector shows fields for JSON objects, form bodies, key: value lines and HTTP headers. A JSON array at the top level, invalid JSON or a text block shows only the Raw tab. Check the JSON is valid, or fence the body with the right tag. See Formats.

#An icon shows as a question mark

The icon name is not in the free Font Awesome 5 set. Check the spelling and leave out the fa- prefix: {fas-database}, not {fas-fa-database}.

#Files and links

#A file will not open

Volley opens .volley and .txt files in UTF-8, and PNG images exported from Volley. A PNG that was edited or re-saved by another program has usually lost the diagram inside it. Drop .har files to import them as recordings.

#A share link says it is damaged

The link was cut short, often by a chat app or email client that limits link length. Ask for the link again as a file, or have the sender save the diagram and share its short link.

#A README image says the diagram was not found

The diagram is private or was deleted. Make it unlisted from the Share menu, or update the README.

#A HAR import has nothing in it

Recordings often contain mostly images, scripts and stylesheets, which are hidden by default. Check that the recording was running while you did the thing, that the browser kept the log across page loads (Preserve log in Chrome and Edge, Persist Logs in Firefox), and try turning on Static assets in the import.

#A drift check checked nothing

Only messages whose text starts with an HTTP method and a path, such as POST /orders, are checked. Rewrite the message text in that form. The method must be uppercase.

#Accounts and limits

#"On this device only"

You are signed in on Free and your one saved diagram is already used. The diagram you are editing is kept in this browser. Delete the saved one from Diagrams, or upgrade to Pro.

#"You reached a Free limit"

You tried something beyond the Free plan. The message names the limit. See Plans and billing for every limit, and when each monthly allowance resets.

#The API returns 401 or 429

401 means the key is missing, mistyped or revoked; create a new one in API keys. 429 means this month's calls are used up; the X-RateLimit-Reset header says when they come back. See Usage and limits.

#Still stuck?

Email support@volley.sh with what you tried. A share link to the diagram, or the .volley file, helps a lot.