{"record":{"id":"69c04d423ba63c2a","repo":"windmill-labs/windmill","slug":"websocket-unknown-message-type-type","errorCode":null,"errorMessage":"[WebSocket] Unknown message type: ${type}","messagePattern":"\\[WebSocket\\] Unknown message type: (.+?)","errorType":"console","errorClass":null,"httpStatus":null,"severity":"error","filePath":"cli/src/commands/app/dev.ts","lineNumber":1409,"sourceCode":"            break;\n          }\n\n          case \"skipSqlMigration\": {\n            // User chose to skip this SQL file\n            const { fileName } = message;\n            log.info(\n              colors.yellow(`[SQL Migration] Skipped: ${fileName}`),\n            );\n\n            // Don't delete file, just move to next\n            if (currentSqlFile) {\n              await onSqlFileCompleted(currentSqlFile, false);\n            }\n            break;\n          }\n\n          default:\n            log.warn(\n              colors.yellow(`[WebSocket] Unknown message type: ${type}`),\n            );\n            respond(\n              \"error\",\n              { message: `Unknown message type: ${type}` },\n              true,\n            );\n        }\n      } catch (error: any) {\n        log.error(\n          colors.red(`[WebSocket] Failed to parse message: ${error.message}`),\n        );\n      }\n    });\n\n    ws.on(\"close\", () => {\n      log.info(colors.cyan(\"[WebSocket] Client disconnected\"));\n    });","sourceCodeStart":1391,"sourceCodeEnd":1427,"githubUrl":"https://github.com/windmill-labs/windmill/blob/e474e8803ce2ff5c2df09a58dab51d45f5c922ca/cli/src/commands/app/dev.ts#L1391-L1427","documentation":"Default arm of the WebSocket message dispatch in `wmill app dev`: a message arrived whose `type` is none of the handled cases (e.g. not sqlMigrationResult/skipSqlMigration). Almost always a version mismatch between the CLI dev server and the frontend dev page, or a malformed client message. Logged and ignored.","triggerScenarios":"Thrown at cli/src/commands/app/dev.ts:1409 when the library encounters an invalid state.","commonSituations":"See trigger scenarios.","solutions":["Update the CLI and the frontend to matching versions so both sides know the same message types","Check for a custom client sending extra WebSocket messages to the dev server","Ignore if the app still hot-reloads correctly — the message is harmless"],"exampleFix":null,"handlingStrategy":"fallback","validationCode":null,"typeGuard":null,"tryCatchPattern":null,"preventionTips":[],"tags":[],"backgroundTag":null,"analyzedSha":"e474e8803ce2ff5c2df09a58dab51d45f5c922ca","analyzedAt":"2026-09-03T12:38:19.024Z","contentChangedAt":"2026-09-03T12:38:19.024Z","schemaVersion":2},"datasetVersion":"2026-09-08T10:18:20.063Z"}