Skip to main content
If something is broken or behaving unexpectedly, this page covers what to try first and how to reach the team.

​
Common issues

The picker shows the models the running deployment has configured. On the hosted product, the available list is curated by the team. On a self-hosted install, it’s whatever your operators have enabled. If a model you expect is not there, ping the team (hosted product) or ask your operator to enable it (self-hosted).
Refresh the workspace. A network blip can leave a node mid-flight. The message will not be lost — open the node menu and re-run.
Check the file size and type. NodePad supports common image and document formats; very large files may be rejected by the storage layer. If you keep hitting the same error, capture the workspace ID and file name and send them in a report.

​
Where to ask

Bugs and feature requests

Email the team with what you saw and what you expected.

Get started

How to sign up and what’s included.

Enterprise / self-hosting

Contact the team via the link in the enterprise overview.

​
What to include in a report

A good bug report has

  • The workspace ID (visible in the URL).
  • The browser and OS.
  • The time and roughly what you were doing.
  • Any error message the UI showed, or a screenshot.
  • For self-hosted reports, the NodePad version and a sanitised log excerpt.