Start with the observed symptom
Separate Verify errors, USB permission, a bootloader handshake, actual disconnects, and a paused Serial Monitor. Keep your sketch and export a backup before troubleshooting. Clearing browser storage can remove local work and does not repair a USB cable.
Prepare a reproducible report
- Record the browser/OS version and selected board/processor/bootloader.
- State the action, the first relevant error and whether the port remained connected.
- Try a separate public Blink or library example and record the result.
- Include a minimal example only if you choose to share it. Remove credentials, private source, account information and personal serial data.
- Keep a local project export so recovery does not depend on a report or cloud session.
A monitored contact address or external issue tracker is not published on this page; no form submission or response-time promise is implied. The diagnostic workflow and guides remain available without an account.
Local work, privacy and school devices
Local sketches are tied to the browser/device and site origin. Optional account/cloud features use their existing access controls. Dot has its separate access and network requirements; code/context is sent through that feature only when you deliberately use it. School policy and host device permissions cannot be bypassed by signing in.
Optional usage measurement is disabled until configured and you opt in. Event payloads exclude source code, project names/contents, serial output and account identifiers. You can change that choice below.
Optional measurement is off unless you have opted in.