Setup Health scans a local workspace for supported Analytics and App Logs mistakes. Each finding points to the affected file and line. Use the findings to correct the local integration before deployment.
Where does Needs attention show up?
Open the workspace home and look for the Needs attention section. It lists every current finding and includes a Check again button. The sidebar carries a collapsible Needs attention card with the finding count. That card also offers Check again and Open settings.
A warning banner appears under Settings, then Analytics, for Analytics findings. The App Logs settings page shows the same kind of banner for logger findings. Both of those banners include a Check again button. These four surfaces share the same in-memory state for the workspace you have open.
Central pages never run this scan and never display it. Select Check again after changing the tracker configuration, logger endpoint, or dependency.
Which setup mistakes can it catch?
Analytics checks require an Analytics site belonging to the signed-in user and workspace name. App Logs checks require a project key and logs that are not explicitly disabled. The scan supports the five findings below.
| Title | Severity | What the scan found |
|---|---|---|
| Analytics tracker is missing | warning | Analytics is enabled, but no supported tracker tag or programmatic configuration was found |
| Analytics site ID does not match | error | A literal data-site-id differs from the tracking ID assigned to this workspace |
| Analytics collector is proxied | error | A non-Aiola data-host-url, rewrite, redirect, route, or proxy forwards collector traffic |
| App Logs SDK is outdated | warning | Installed or locked @aiolaapp/logger is older than the latest npm version |
| App Logs uses a legacy endpoint | error | An endpoint option or AIOLA_ENDPOINT... value uses app.aiola.com or /functions/v1/app-logs-ingest |
How do you fix an Analytics tag?
For a missing tracker, Fix with agent opens a thread with the exact tag. Its prompt asks for the correct app shell without unrelated changes. Copy snippet places the same tag on your clipboard. Add the tag to the shared page head if you install it manually.
For a site ID mismatch, Fix with agent starts a thread with the assigned ID and a corrected tag. Use the public tracking ID in the tag, along with the allowed domain. Analytics does not use the secret project key shared by App Logs and Feedback.
For a proxied collector, Fix with agent asks to remove the collector rewrite, proxy, and data-host-url. Retain the script served from cdn.aiola.app/analytics.js. A proxy that only delivers that script file can remain. Proxying collector traffic hides the visitor, losing country and city information. Events should post directly to https://aiola.app/api/collect.
How do you fix the App Logs SDK?
An outdated SDK offers an Update to v<latest> button. Aiola runs the detected package manager inside the package directory.
- npm uses
install @aiolaapp/logger@latest. - pnpm, yarn, and bun use
add @aiolaapp/logger@latest.
The package directory must resolve inside the workspace you have open. Its package.json must list @aiolaapp/logger in dependencies or devDependencies.
The update command can run for up to five minutes. You receive only the last 40 lines of output. Inspect the result's success, current, latest, stillOutdated, and output fields to check the update outcome.
A legacy endpoint has its own finding and fix action. Fix with agent asks to use https://aiola.app/api/app-logs-ingest for ingest. You can also remove the endpoint option so the SDK default applies.
When does a finding go away?
Setup Health has no dismiss control on any finding. Previous saved dismissals are removed. A finding stays visible until a new scan no longer detects that issue. Opening a fix thread by itself does not clear the warning.
Check again bypasses the workspace cache and clears the cached npm latest version first. The app otherwise scans each workspace once per process, when you first open it. It does not poll on a timer or when the window gains focus.
Workspace results and the npm version lookup each stay cached for one hour. Registry lookups for the latest logger version time out after 5,000 ms. A successful logger update drops both caches and forces a new scan.
Who can run the scan?
You need a signed-in Aiola account on Pro Monthly or Pro Yearly. An active trial also passes this plan check while its end time is still ahead. Pro costs $24 a month or $240 a year and includes 100k events. GUI Lifetime, listed on the pricing page at $49, $89, or $129 once, does not unlock this scan. The free download still lets you install the desktop app.
Your workspace must be local and must have a root path on disk. An SSH workspace is skipped by this scan. A signed-in session is what resolves the Analytics site and the project key.
What does a clean scan leave out?
The disk scan reads at most 6,000 files. It skips any file larger than 512 KiB. Content past 48 MiB in total is left unread. Fallback directory walking goes no deeper than 8 levels.
Dependencies, build output, and Git data are excluded from the read. Tests, fixtures, and the bundled analytics.js file are excluded too. A clear result means none of the supported findings showed up inside those limits. It does not prove your deployed site is collecting events. Check incoming Analytics and App Logs data on the live deployment separately.
The Setup Health documentation lists the scan endpoints, response fields, and package-update requirements.
Try it in Aiola from the free download. The desktop app supports macOS 12 or later and Windows 10 or later. A Linux build is not available for this desktop app. Install desktop version 2.0.8, then open the workspace you plan to ship.
