Troubleshooting

Beacon states why a figure is unavailable rather than leaving a gap. Each heading below is what you see, followed by what caused it and what to do.

​

Nothing activates after setup

Cause. Billing is not connected, or its connection has not completed. Billing is the only required source, and no figure is produced without it. Fix. Connect a billing source and complete authentication in that tool’s own login screen. Every other source is optional and can follow.

​

A figure reads “source not connected”

Cause. The figure depends on a source that is not connected. The message names which one. Fix. Connect the named source. The figure resumes on the next read. Connect your tools lists what each source turns on.

​

A figure reads “not calculated yet”

Cause. The figure exists, and this period has not been computed. Beacon serves values it computed on schedule and does not calculate one to satisfy a request. Fix. Wait for the next computation. How often that happens follows the source’s connection method — see Refresh.

​

Figures switched off after working

Cause. A connected source stopped responding. Access revoked in the source tool, a changed authentication, or an outage at the source will each do it. Dependent figures switch off and name the source rather than narrowing their basis silently. Fix. Reconnect in the source tool. The figures resume without further action.

​

A figure is older than expected

Cause. The source connects by scheduled export or through an aggregator, so its data arrives daily or weekly rather than continuously. Fix. Read the freshness stated on the screen; it is the actual age of the source behind the figure. A weekly export is never presented as a live figure. Where a faster method exists for your system, it is set at connection.

​

A reader is told a figure is “older than your freshness limit”

Cause. The value is available but staler than the limit set on that reader’s grant. Fix. Raise the limit on the grant, or connect that source by a faster method.

​

A reader is told a figure is “outside what this reader may see”

Cause. The value exists and is beyond the access granted to that reader. Fix. Widen the grant’s families of information, accounts, or sealed-or-live setting. A request outside a grant is refused whole, never partly served.

​

A reader stopped working with no warning

Cause. Its grant was revoked or reached its expiry. Revocation takes effect on the next request, with nothing cached on the far side. Fix. Issue a new grant. Existing grants and their expiry dates are listed where they were created.

​

A request for a company Beacon has not seen is refused

Cause. The company has no history in your connected systems, so there is nothing to calculate from. Fix. Use the exported model instead — dimensions, weights and thresholds — and apply it in the tool that holds that company’s data.

​

A value in your CRM reads high, medium or low instead of a number

Cause. Modelled figures write as bands. A CRM field carries no definition, confidence or freshness, and a bare score there reads as a measurement. Fix. None needed. Read the underlying value in Beacon, where it arrives with its definition and freshness attached.

​

A financial figure is missing from your CRM records

Cause. Financial figures are off by default for CRM write-back. A value written onto a CRM record is visible to everyone with a seat in that tool. Fix. Enable it on the field set. The prompt states what becomes visible before you confirm.