When the screen says it is unsure, believe it.
NovusLens would rather tell you what it cannot say than fill the gap with reassurance. This page explains the messages you may see, what each one means, and what to do. None of them is an error in the sense that something has been done to your systems. NovusLens maps and advises; these are statements about the evidence.
The age of the picture
The strip at the top of the mapMapThe view of teams, services and their dependencies for the selected part of the organisation. Details appear beside the map. says records as of and an age. This age describes the latest background projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default. pass. That process updates the twin every thirty seconds by default. A confirmed browser import also updates the map before returning. Those records can be newer than the last background pass.
| You see | It means | What to do |
|---|---|---|
projection not keeping up | The age is more than three minutes. The update process has fallen behind and the figure is older than it should be. | Ask the operator to check readiness on the installation. See troubleshooting. |
records refresh only when someone saves | No projection pass is recorded. The loop is not running on this installation, so the picture changes only when someone saves. | Ask the operator whether the projection service is meant to be running. |
analysis incomplete on the last pass, with a stage name | The records were projected, but one analysis stage failed. What you see may be older than the records. | For Docker, inspect the /ready response in Installation diagnostics. Installer status lists setup progress and containersContainerA running program with its own packaged software and isolated environment, managed by Docker on the host.. |
the operator has a volume warning | The read modelRead modelThe database tables used by the map, Ask and Find. NovusLens rebuilds these tables from its history of recorded changes. raised a warning about size. | Pass it to the operator. |
Coverage incomplete
On an agent’s remitRemitA written list of an agent’s allowed actions, resources and destinations for information. The list states whether it is complete. panel, a fleetFleetA group of AI agents considered together. Related activity can be grouped only when the records establish what the agents share. may be marked coverageCoverageWhat the available records cover, and what is missing. A count such as “3 of 5 dependencies measured” names the measured portion and the gap. incomplete — no all-clear. Every activity observation states which streams its source covered and whether coverage was complete. If any observation lacks a stream, the panel withholds the claim that nothing else happened.
Each observation still shows its own result. What is withheld is the reassurance. Silence from a source that stopped collecting is inconclusive, and NovusLens never reads it as good news. To clear it, ask the source’s owner to cover the missing stream, or to state honestly that it cannot.
Review required: authority not established
For an agent’s remit, there are five outcomes. Four make a statement: inside the recorded remit, outside it, recorded remits that overlap and are not resolved, and cannot be stated.
Review required: authority not established appears when no eligible remit applies, or an incomplete remit cannot settle whether the observed activity was permitted. An incomplete list never proves a prohibition, so NovusLens says neither inside nor outside. An activity the remit explicitly excludes is different: it reads outside whether or not the list is complete.
This is a state, not a findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner., and it sends no notification. Ask the responsible person to confirm the permitted activity and whether the list is complete. If the right remit exists but is not available, ask the operator to review its issuer enrolmentEnrolmentThe operator's recorded permission for a source to send specified record types about named agents, using an identified signing key.. Then reopen the activity. Do not mark a list complete only to clear the message.
First measurement
The finding Dependency measured for the first time appears when a couplingCouplingA link where one team or service depends on another. Its Loose, Buffered or Rigid class describes the time needed for a handoff. that was recorded as unknown has now been measured. There was no earlier estimate to compare, so it is not a contradiction. The suggested step is to check the measured handoffHandoffWork or information passed from one team or service to another. Its measured or stated completion time determines the dependency class. with both teams and resolve the finding with what you conclude. See findings.
Estate drift
Your estate is described twice: by the infrastructure codeInfrastructure codeFiles that describe the computing resources an organisation intends to create and how they should be configured., which says what it is meant to be, and by the provider’s export, which says what exists. Where they disagree, NovusLens records a finding. Neither side is corrected, and nothing in your estate is changed.
| Finding title | Meaning |
|---|---|
| In the cloud account, not in the infrastructure code | The provider reports a resource inside a container a tool manages, and the tool’s code does not describe it. A manual console change looks like this. |
| In the infrastructure code, not reported by the provider | The code declares a resource the export does not report. The code may be ahead, or the export may be partial. |
| Infrastructure code and provider describe the resource differently | Both describe one resource and disagree about it, for example its region. |
Read the coverage on the finding first. It says how many declared resources could be compared, how many could not and how many reported resources were in scopeScopeThe work, data, activity or access that a rule, statement or calculation covers. For access, it names the records an account can see. For team measures, “Own operations” covers the selected unit. “Including descendants” adds the units beneath it.. A sweep that finds nothing may mean the two agree, or that nothing was comparable. Resources match only when their deployed names are exactly the names recorded in the code. Only providers and domains your code covers are compared.
The sweep runs as part of the link step after the estate documents load. See the estate export.