---
title: "Support · RUAL Documentation"
description: "Get help with RUAL: the checks that solve most problems, what to include in a report, and where to go when you are still stuck."
canonical: https://docs.rual.nl/support
language: en
---

# Support

Something not working, or documentation that does not match what you see in RUAL Studio? Start here. Most issues are solved by the checks below, and the rest reach us faster when you bring the right details.

### The documentation is wrong or unclear

Use the **Tell us what to improve** link at the bottom of any page. It opens a short form that sends the page you were reading along with your message, so we can fix the exact paragraph you were looking at. No account or ticket needed.

### Before you report a platform problem

These four checks resolve the majority of reports, and they are also the first four questions we would ask you:

- **Is the blueprint activated?** A saved blueprint does not respond until you hit `Activate` in the top bar. Endpoints and pages stay silent otherwise.

- **Are you testing the deployed or the saved version?** Append `?development` to call the saved version. Without it you are hitting the last deployment.

- **What does the console say?** The blueprint console shows the executed path, the error pin, and the values that flowed into it. See [Debugging Blueprints](https://docs.rual.nl/troubleshooting/debugging).

- **Did it work before?** Compare against block revisions and the audit log to find the change that broke it. See [Common Issues & Fixes](https://docs.rual.nl/troubleshooting/common-issues).

### What to include in a report

A report with these details is usually answered in one round instead of three:

| Detail | Why we need it |
| --- | --- |
| Cluster URL | Identifies the environment and its core version. |
| Core version | Shown in the sidebar card and on the [core versions](https://docs.rual.nl/core-versions) pages. |
| Blueprint name and `guid` | Lets us find the exact flow instead of guessing from a screenshot. |
| Timestamp of a failing run | Makes the run findable in the cluster logs and the API history. |
| Steps to reproduce | What you clicked or called, what you expected, what happened instead. |
| Error text or error pin output | The literal message, not a paraphrase. |

Never send passwords, access tokens or refresh tokens. If a token is involved, send its `guid` from the token list instead of the token itself.

### Where to go next

### Still stuck

If the checks above did not resolve it, contact the RUAL team through [rual.nl/support](https://rual.nl/support) with the details from the table above. Access requests for a cluster you do not have an account on go through an administrator inside your own organisation, not through us.

### Frequently asked

**How do I report a problem with RUAL?**

Run the four checks first: is the blueprint activated, are you testing the development or the deployed version, what does the console say, and did it work before. If it still fails, report it with the cluster URL, core version, blueprint guid, a timestamp of a failing run and the exact error text.

**How do I report an error in the RUAL documentation?**

Use the Tell us what to improve link at the bottom of any documentation page. It opens a short form that sends your message together with the page you were reading.