When recorded work can be scored¶
Recording a work event and scoring it are separate operations. HiveOrbit may retain an event while setup or access information is incomplete. Retention does not mean that points, recognition or an analytical result have been created.
This page describes the newer backend admission and recovery rules. Its connected frontend journey and environment delivery remain unverified. Preparing and enabling HiveOrbit explains the administrator's activation decisions; the source-processing overview explains the wider evidence pipeline and calculation limits.
Work-source readiness explains how completed-day inventories distinguish arrived evidence from completed scoring.
Two times matter¶
HiveOrbit checks when the work occurred and whether the organization can process it now. Work must fall inside an admitted activation period and not before the synchronization baseline. A currently active period and valid operational prerequisites are also needed before processing proceeds.
For example, work from an earlier admitted period may arrive while HiveOrbit is paused. It can wait for processing even though its occurrence was inside an eligible period. Work that occurred in the gap between two periods is different: starting a later period does not make that gap eligible. The period includes its start instant and excludes its end instant.
Scheduled activation therefore does not score work before its chosen start. Restoring a product entitlement or repairing organization settings does not independently reopen a period that was suspended. An administrator must make the required reviewed activation decision.
When organization access is interrupted¶
A temporary failure to check the organization's access can leave work waiting without confirming that its activation period has ended. Confirmed loss of organization access, HiveOrbit entitlement or required setup conditions can suspend processing. Support needs the actual reason; the absence of a score alone does not establish which condition occurred.
The platform also records effective organization-status history. If an interruption arrives late, HiveOrbit can shorten an earlier activation period to the interruption's actual start, even if no work arrived during the gap. A planned start inside that interruption can be cancelled. A later reviewed activation outside the interruption remains valid; restored access alone does not reopen the interrupted period.
For example, if access was interrupted at 10:30 and restored at 10:45, that restoration does not automatically resume the earlier scoring period at 10:45. A reviewed activation at 12:00 can begin a new period. These eligibility changes do not themselves recalculate completed scores or undo recognition. Existing results and pending work require their own processing checks.
Understand an event's outcome¶
| Outcome | Meaning and recovery boundary |
|---|---|
| Waiting for admission | The event has been retained, but setup, current access, reference information or eligibility is unresolved. It has not earned a score merely by waiting. |
| Excluded | The occurrence is outside an admitted period, before the reference baseline, or a required person's licence was explicitly ineligible at that occurrence. A later ordinary retry does not automatically reopen an already excluded receipt. |
| Processing already started | Existing progress and proofs can be retained while a later admission check blocks further work. That is not the same as a newly queued event. |
| Completed | The existing processing result is handled through the normal duplicate/revision rules. Repeating an event is not an instruction to award recognition again. |
| Invalid evidence | Contract or integrity failures follow the separate rejection and quarantine path. Enabling HiveOrbit does not make malformed evidence valid. |
These are different reasons for absent or incomplete results. None should be displayed or explained as a verified zero contribution. The recorded state also needs durable processing and successful downstream reads before an environment can present a result reliably.
People and licences at the time of the work¶
The admission check resolves each distinct participant and the event's actor to one effective employee record for the organization. It uses that employee's associated user identity to find the applicable HiveOrbit eligibility at the occurrence time. A work record's contributor identifier is not always the same identifier as the authenticated user.
Missing employee or licence information leaves the event waiting. Explicit ineligibility excludes it. Ambiguous employee mappings require diagnosis; the service does not choose an arbitrary matching person. Buying or restoring access now is not by itself proof that the person was eligible for an earlier event.
Reference resolution preserves the original work evidence. It does not rewrite the event to make an identity match. If the wrong person appears to be associated with work, ask the responsible administrator or support team to investigate the source record and effective employee history.
How retained events are revisited¶
Activation requests background recovery. Normal reconciliation maintenance can also retry retained intake after a scheduled start becomes due or after a temporary authority outage clears. Recovery is bounded and may need several batches; an activation acknowledgement is not proof that all retained work has been processed.
Recovery validates the retained event before redispatching it through the normal admission and scoring path. It can still wait, be excluded or fail another processing requirement. Already excluded receipts and partly processed receipts are not the same queue as newly waiting admission receipts. They may require a different diagnostic path.
A blocked or corrupt batch needs investigation. Repeatedly activating the feature, refreshing a dashboard or creating duplicate source work does not repair retained bytes or guarantee recovery. Use the organization's support process and preserve safe event references and the relevant occurrence period.
What managers and executives can conclude¶
An activation date establishes an eligibility boundary, not an instant reporting-completeness promise. An empty period may reflect missing evidence, pending admission, exclusions, unresolved identity, further processing or a failed read. Check the explanation and source context before comparing people or periods.
Work-source health and current setup readiness are related but distinct. A completed-day synchronization result used to enable HiveOrbit does not certify every future live event. Today's operational health does not establish that all historical periods have finished processing. A permitted destination also does not guarantee that its data is currently available.
Keep the existing calculation and source limits in view. These admission rules establish whether work may proceed to processing; they do not by themselves resolve period accumulation, evidence interpretation or the business fairness of a comparison.