Skip to article
/ docs

Search documentation

Popular starting points. Search all 37 articles.

  • Get startedProduct availability and preview limitationsUnderstand what works in the frontend and which product capabilities are not connected yet.
  • Get startedBuild your first RAG pipelineBuild and inspect your first seven-node Basic RAG graph and learn what validation means.
  • Build pipelinesBasic RAG and Hybrid Search templatesCompare Ragify's two starting graphs and decide which pattern to explore.
  • Node referenceUnderstand the node libraryBrowse the ten registered node types by role in the workflow.

↑ ↓ to navigate · Enter to open · Esc to close

Back to Ragify ↗
On this page

Documentation

Frontend preview support

Troubleshooting

Resolve common design-time questions and distinguish interface previews from backend failures.

My pipeline passes validation, but I get no answer #

Graph validation checks supported frontend constraints. It does not run retrieval or generation. The current Test Query interface can report that the execution backend is not connected. This is expected for the reviewed frontend.

My selected document is not searchable #

Document selection is metadata-only. File parsing, chunk generation, embeddings, storage, and search have not been connected to a backend.

I returned later and my graph is missing #

Graphs are session-scoped and do not have server persistence. Reopen a starting template for a new design session. Do not assume saved status from UI text alone.

A node will not connect #

Check the order and type of the stages. The current graph accepts a single linear chain and one retrieval strategy. Follow the Basic RAG or Hybrid Search template and use validation feedback to identify incompatible connections.

The editor is difficult to use on my phone #

The full canvas is desktop-oriented. Smaller screens may use a simplified onboarding handoff or dashboard path. Use a desktop browser for detailed graph work in the current preview.

My API sample or key doesn't work #

API snippets are illustrative. Deployment and operational API key creation are not implemented. Do not debug a sample URL as though a server were already listening.

A provider dialog asks for configuration #

Treat provider dialogs as previews. Do not enter production credentials until a secure backend flow is explicitly available and documented.

Theme changes are not synchronized #

Appearance and workspace display preferences are browser-local, not authenticated cross-device settings.

Still blocked? #

Record the page URL, node type, action taken, expected behavior, actual behavior, and browser details. Avoid including actual tokens, keys, or private document contents in a bug report.