Errors 340xxx

How Flipnote Studio reports HTTP responses and internal transport failures.

What this means

The original Flipnote Studio V2 client has separate ways to report an HTTP error and an internal transport error.

For an HTTP response handled as an error, the displayed code is 340000 plus the HTTP status. HTTP 404 produces 340404 and HTTP 503 produces 340503. An internal transport error instead uses 340600 plus the internal error number.

Common HTTP results

  • 340301 or 340302 — a redirect response reached error handling. Record the action that triggered it so staff can check the destination.
  • 340400 — the server rejected the request as invalid.
  • 340401 or 340403 — authentication or access was refused. Follow any message shown on the DSi.
  • 340404 or 340410 — the requested resource was unavailable.
  • 340408 or 340504 — the server or a gateway reported a timeout.
  • 340429 — the server limited requests. Wait before trying again.
  • 340500, 340502 or 340503 — the server or its gateway reported a failure or temporary unavailability.

The same number can appear when requesting a menu, image, Flipnote or an action's response. It does not always identify which part of the page failed. For 3406xx, use the transport-error guide.

What to try

  1. Read the complete message and try the same action once more, after any requested wait.
  2. Check whether other RexiMemo menus and Flipnotes open.
  3. If the error followed an upload or comment, check whether it was posted before resubmitting.
  4. If it repeats, contact RexiMemo support with the full code, the action, the approximate time and the affected Flipnote's web link.

Technical reference

These explanations draw on the original Flipnote Studio V2 client research in Flipnote World — Hatena responses and errors.