Administration Troubleshooting
This guide covers the most common administration symptoms in AlloyScan and how to verify and resolve them. Each entry follows a consistent pattern: symptom, likely cause, where to verify, and resolution steps.
Symptom: Inventory grid shows a "1000-record cap" banner
Likely cause: The default grid cap of 1000 rows is in effect.
Where to verify: The cap banner displayed at the top of the Inventory grid.
Resolution: 1. Use column filters to narrow the result set so the visible rows are below the cap. 2. Click Load all only when justified — loading all rows is performance-heavy. 3. Where appropriate, save the narrower view as a personal or shared view from the view-name dropdown.
Symptom: Dashboard widgets are slow to refresh
Likely cause: Concurrent scan/audit workloads are saturating the Audit Service host.
Where to verify: Admin Center > Site Settings > Tasks and services > Active tasks.
Resolution: 1. Wait for the Active tasks queue to drain. 2. Stagger your scan and audit schedules so they do not overlap. 3. If the load is persistent, install a second Audit Service host and assign it to a subset of Segments.
Symptom: "Audits per month" quota is exhausted
Likely cause: The Site has hit its monthly cap on audits.
Where to verify: Admin Center > Site Settings > Limits and usage > Audits per month.
Resolution: 1. Wait until the recharge day for the counter to reset. 2. As a Global Administrator, raise the per-Site Max for audits per month at Admin Center > App management > Billing. 3. Review schedules to remove unnecessary recurrent audits.
Symptom: API client receives 429 (throttled) responses
Likely cause: The server-side API workload ceiling has been hit, or the per-month API transaction quota has been exceeded.
Where to verify: Admin Center > Site Settings > Limits and usage > API transactions per month, plus the response headers returned to the client.
Resolution: 1. Apply exponential back-off in the client and retry. 2. Distribute the load across time rather than running large bursts. 3. If the per-month counter is near its cap, raise the Site quota (Global Administrator only).
Symptom: Audit Service shows the suffix "- outdated" in its modal title
Likely cause: The Audit Service binary is running an older version than the AlloyScan frontend.
Where to verify: Admin Center > Site Settings > Tasks and services > Audit services > (service) — the modal title displays the version and the outdated marker.
Resolution: 1. Update the Audit Service binary on the Windows host that runs it. 2. Confirm the host can reach the AlloyScan instance over HTTPS/443. 3. After upgrade, reopen the service detail to confirm the marker is gone.
Note: An outdated Audit Service is a soft state — it continues to run.
Symptom: A scan or audit log row is missing or stuck
Likely cause: The triggering Segment has no Audit Service assigned, or the assigned service is Inactive or ScheduledForDeletion.
Where to verify: Admin Center > Site Settings > Tasks and services > Audit services, plus the Segment Open view.
Resolution:
1. Confirm the Audit Service is Active (the host is online and reaching the instance).
2. Reassign the Segment to a healthy service if necessary.
3. Re-run the scan or audit.
Symptom: A specific Admin Center menu entry is missing
Likely cause: The menu surface is not enabled for the deployment, or the user lacks the role required to see it.
Where to verify: Compare the user's role with the expected scope, then check with your deployment operator whether the menu surface is enabled for the instance.
Resolution: 1. Confirm the user is signed in with the appropriate role (Administrator, Global Administrator, or User). 2. If the role is correct, ask your deployment operator to verify that the corresponding Admin Center surface is enabled for the instance.