Check source health and investigate missing evidence¶

Source Health helps an authorized administrator understand delivery, processing and reconciliation of the records used by HiveOrbit. It describes the condition of those records. It does not measure an employee's performance or provide a repair console.

The steps below follow the current final designs. The frontend is still in progress, and production population of the source-health records has not been established by the inspected implementation. A design example or an empty screen does not prove that monitoring is operating in your organization.

Before you begin¶

Confirm the organization and your permission to view Source Health. Permission to view contribution insights, recognition or configuration does not automatically grant this access. Identify the work item, approximate occurrence time and period you want to investigate.

Use the source-health overview to understand the terms. For a missing or unexpected contribution, also review supporting evidence and the person's applicable role assignment, where you have permission. These pages answer different questions.

Open Source Health¶

1. Open HiveOrbit for the organization.
2. Under Administration, select Source Health.
3. Read the organization or reporting scope shown by the page.
4. Wait for the requested view to finish loading before interpreting its cards or rows.

If the destination is absent or restricted, ask your administrator to check access. Do not use another person's account or assume that an organization-wide summary grants access to every employee or source document.

Choose a period and filters¶

1. In View context, choose Period and Selected period.
2. Leave Source at All sources, or choose the relevant returned source.
3. Leave Health at All health states, or select a state you want to investigate.
4. Choose the lag order, such as Longest delay first.
5. Check the Workspace calendar, then select Update view.

Each request describes one selected period. The data-day rows represent UTC source partitions, while the workspace calendar and displayed timeline can use the organization's timezone. Near a day or month boundary, preserve the displayed period and timezone when reporting an issue; do not assume that a UTC data day begins at local midnight.

Changing the source, health filter, period or sort should start a fresh page sequence. Use the returned choices rather than assuming that every configured work source has a record for every day. If the selected period is too large to summarize, choose a shorter period; a narrower source filter does not avoid the initial record limit.

Interpret the summary¶

The cards follow the filters. Selecting Healthy can therefore show zero records needing review even when other, filtered-out records have problems. Clear the health filter to return to the broader view. An empty result is not a finding that all expected sources are healthy.

Select and read a source record¶

1. In Source Health Records, identify the source and Data day.
2. Review its kind, completeness, delivery delay, processing delay and returned health state.
3. Select the row to open its details below the table.
4. Use Previous and Next only when available. Selecting a row reviews information already returned with that record; it does not start reconciliation or replay.

The narrower desktop design shows fewer table columns. Read the selected record's details for the complete returned information rather than treating an omitted column as a missing measurement.

Required, Advisory and Technical describe the source's classification. They are separate from its health and launch-readiness impact. A Required label does not by itself mean that the organization cannot open HiveOrbit.

Understand completeness and delays¶

The detail shows how many expected records have been projected into HiveOrbit and a completeness percentage. Delivery and processing are separate stages: receipt means a record arrived; projection means it contributed to the stored analytics representation.

Read the percentage together with health, reconciliation and warnings. A record can show 100% completeness while still containing invalid records, pending reconciliation, reference gaps or corrections. When no records were expected, the current calculation can also show 100%; that is not proof that every business activity was captured.

Delivery delay is derived from the latest source occurrence and receipt times when available. Processing delay is derived from receipt and projection times. These values are not averages, percentiles, the age of the oldest outstanding record or a promised recovery time. The current health rule treats any positive delay as Delayed; it does not compare that value with the catalog's delivery target. Rounded display values can hide a small positive delay.

The Source timeline separates the latest source activity, receipt and availability in HiveOrbit. Missing timestamps should remain unavailable. Do not replace them with the current time or infer a successful stage from a later-looking design example.

Read reconciliation and reference continuity¶

Reconciliation compares the source's retained inventory with independently retained evidence in HiveOrbit. Reconciled means that comparison found no differences under its current checks and limits. A later mismatch can invalidate an earlier reconciled result. It is not a guarantee that every real-world activity was recorded by the source.

When investigating an item that has no contribution, ask support whether it was accepted, excluded under a recorded eligibility/history rule, still waiting for admission into processing, or incomplete/invalid. A valid exclusion can be accounted for by reconciliation without producing a score. Work waiting for admission remains unresolved; it should not be described as lost, corrupt or already repaired merely because it is retained.

Keep the original work reference and relevant period. Ask for the actual exclusion or waiting reason before changing a person's assignment or repeating the work. Another read or comparison can reflect a later resolution, but it does not itself admit pending work or create an award.

Reference continuity concerns supporting information such as employees, reporting hierarchy and licence eligibility. The detail can show its source, continuity state, last continuous update, latest update seen and missing updates. A source record's displayed reference information selects one relevant stream; it is not a complete health summary of every dependency.

Read warnings for duplicates, rejected records, missing records, corrections, reconciliation and reference gaps. The current design labels one count Corrected, but the returned value represents pending corrections. Do not interpret it as completed repair. The wording needs reconciliation in the final implementation.

This page has no replay or repair action. Refreshing it requests another read; it does not fix source data, fill a reference gap, clear quarantine or force a calculation.

Understand launch impact¶

The selected record can show one of three messages:

• Affects HiveOrbit launch readiness: the record is included in the current launch-readiness check and has a relevant blocker.
• No launch-readiness impact: this record does not block that check. Other records or prerequisites can still block readiness.
• Launch impact unavailable: the relationship could not be established. Treat this as unknown, not as permission to assume readiness.

The relationship depends on the catalog, the current UTC data day and specific operational problems. Delay alone, a historical record or the Required label is not sufficient to infer it. Preserve the explicit returned message even when it differs from your first impression of the health badge.

Interpret reporting coverage¶

Reporting coverage lists people whose current role assignments use the source and whose current activity, licence and reporting scope permit them to appear. It is not an exhaustive list of people who performed the historical work, a performance assessment or proof that their full required evidence is available.

The list can be empty for a technical source, an unmatched role rule or because nobody in your permitted scope matches. Historical periods still use current membership for this list. A name appearing here does not grant access to that person's evidence or original work.

Recover from an empty or failed view¶

Request support with useful context¶

Provide the organization, source display name, data day, selected period, timezone, filters, health state and warning text. Include the original work reference and occurrence time when appropriate and authorized. Explain whether the issue concerns missing evidence, delayed processing, a reference gap or an unexpected calculation.

Support and operators must verify the actual environment and use the source-owned recovery procedure. Historical authority conflicts, quarantined messages and data repairs need a separately scoped operational decision. Avoid attaching unrelated employee information or confidential evidence when a reference and error message are sufficient.