Docs When something doesn't work
Relia shows no data
Find out why your app runs but Relia shows nothing, and get your first requests and visits to arrive.
Your app runs, but Relia stays empty. Relia does not show an error for this: data sent with another project's id lands in that project, and data sent with a key from another project is refused without a message in your app. Work through the checks below in order. Most fixes take a minute.
What you'll see
Open your project in Relia, then the Setup tab. The card Is Relia receiving everything? shows one row per part of your app:
- Requests from your server: requests per service from the last 7 days.
- Visits to your web app: browser sessions from the last 7 days.
- Source maps (readable browser errors), and the optional rows Who your users are and AI agent runs.
Each row says Not yet, Arriving (data in the last hour), Received, or Optional. When nothing has arrived, the card's title says Waiting for data. Each missing row shows the one step left.
Tip: your AI assistant can run the same check. Ask it "Is Relia receiving everything?" (it calls
relia_check_setup). See Connect your AI assistant.
Find the cause
Try these in order. After each one, use your app (open a page or call an API), wait a minute, and look at the Setup tab again. It updates by itself.
- Did the app restart after setup? The SDK only starts with the process. Stop the app and start it again.
- Is there traffic? Relia shows requests and visits, not idle servers. Open a page or call one of your endpoints.
- Is it the right project? The project id in your app must be your project's id (shown on your project page under Setup Guide & SDK). Look at
RELIA_PROJECT_IDin.envor.env.local, or theprojectId/project_idinrelia.tracing.jsorsrc/relia.ts. An id from another project sends data to that project. - Is it the right key? A project key (
RELIA_KEY, starts withrelia_live_) from another project is refused. A missing key is still accepted. The quickest fix for 3 and 4: run the setup again and pick the right project, or copy the id and key from Setup Guide & SDK. - Is Relia loaded first? (Node.js) The generated
relia.tracing.js(orinstrumentation.tsin Next.js) must run before your framework is loaded. If it is required after Express, Fastify or similar, requests are not seen. - Is the deployed app set up too? Your
.envand.env.localfiles are usually not deployed. Add the sameRELIA_*values to your host's environment variables (Vercel, Render, Railway, Forge…), then deploy again. - Can your server reach Relia? A firewall or company network that blocks outgoing traffic stops everything. Your server must be able to reach Relia over HTTPS.
- Is monitoring switched off? In the project's Settings, Advanced, SDK settings, the Monitoring switch pauses every SDK of the project within 10 minutes. Sessions recorded below 100 % keeps only part of the visits.
Tip: watch Control what Relia collects: sampling, ignored pages, kill switch (2 min).
Less common causes
- Old SDK on Windows or Node.js 17 and later. Versions of
relia-sdkbefore 0.5.1 could fail without a message when the address waslocalhost. Update the package:npm install relia-sdk@latest. - Your app already uses OpenTelemetry. Relia adds itself to your existing setup when it can. When it can't, it prints the endpoint and the
relia.project_idattribute to add to your own exporter when the app starts. Look for a line starting with[relia]in your app's output. - Over the monthly limit. Relia never stops at the limit: new data is sampled (about 1 in 10 kept, errors and slow requests always kept). You still see data, just less of it. See Plans and limits.
Check it worked
The Setup tab shows Arriving for the part you fixed. When every part your app has is in, the title says All set. The first requests usually show within a minute.
Still empty?
Ask for help from Help & support in the app's menu. Include the service name, the language and framework, and what the setup printed. See Get help.
Next
Last checked against the product: 1 Nov 2026