Understand work-source readiness¶
HiveOrbit compares the work records reported by each source with the records it has received. This helps distinguish a day with no reportable activity from a day whose evidence is missing. The comparison supports setup and operational diagnosis; it does not judge an employee's performance or prove that every business activity was recorded correctly.
This page explains the newer backend rules. The frontend remains in progress, and no deployment or new screen sequence is established here. Setup explains the administrator's decisions. Scoring eligibility explains why received work can wait, be excluded or proceed.
Three different questions¶
| Question | What the answer establishes | What it does not establish |
|---|---|---|
| Has the source supplied its inventory? | The source has described the work records for a particular completed day, including an explicit empty result when appropriate. | That HiveOrbit has received and processed every listed record. |
| Does received evidence match that inventory? | The expected identities and content can be compared with retained evidence and its processing state. | That every retained record should earn points or that its business interpretation is correct. |
| May scoring begin or continue? | Setup, organization access, role expectations, activation periods and the other processing requirements permit the next operation. | That a dashboard is already up to date or every employee has a measurable result. |
For example, two work records may have arrived while HiveOrbit is being prepared. If their contents match the source inventory, they can help establish that synchronization is ready even while they are waiting for activation. The ordinary operational comparison still identifies that waiting work. There is no need to invent a score to prove that the records arrived.
A completed day and an empty day¶
Source inventories use completed UTC days. They are separate from the organization's reporting week, headquarters timezone and campaign periods. Work recorded today can still be processed through its normal path, but today's unfinished UTC day cannot supply the completed-day setup proof.
An empty day needs an explicit inventory stating that there were no reportable records. An absent response, missing part of an inventory, disconnected service or empty chart is not the same result. A mismatch can involve a missing record, changed contents, an unexpected extra record, an unresolved correction or invalid evidence.
Setup needs the complete required source set for one common completed day. It considers the latest available result for each source within the preceding two completed UTC days, with a verified capture from the last 24 hours. If sources report different latest days, setup may remain unready even when some older results overlap. This is a readiness rule, not a promised synchronization time.
Why a source can be checked again¶
The source preserves the identity and contents of its original day inventory. A later unchanged capture can establish that the same inventory was checked after the day ended or checked more recently. It does not rewrite the original publication time, change the list of work records or award additional contribution.
Changed inventory contents cannot be accepted merely by attaching a newer capture time. Older duplicate messages also cannot replace a newer accepted capture. Support must diagnose a genuine content conflict through the source and reconciliation process; repeatedly starting setup is not a way to erase it.
Waiting, exclusion and completed processing¶
| Evidence outcome | Meaning for the comparison |
|---|---|
| Completed processing | The retained record has matching processed evidence and sufficient recorded revision progress. Other comparison checks still apply. |
| Excluded for a supported reason | The record can be accounted for without creating a score. Examples include work outside eligible activation periods or a participant's licence not applying at the occurrence time. |
| Waiting for activation or another admission prerequisite | The record is retained and accounted for, but ordinary reconciliation remains pending. Setup can recognize this limited waiting state when all other proof checks pass. |
| Incomplete, invalid or quarantined evidence | The comparison cannot claim completion. A missing prerequisite, content discrepancy or processing failure requires diagnosis. |
An exclusion is not an employee performance penalty. A waiting record is not a successful score. Permission or licence restoration does not make every excluded record eligible retroactively; the admission rules describe the time and retry boundaries.
After processing progresses, maintenance can revisit older comparisons that were waiting for admission. Recovery and comparison are separate operations. Their scheduling does not establish a completion deadline, and a persistent older problem can delay which later comparison is selected.
When support is needed¶
Retain the organization, affected work source, work date, visible status, safe request reference and the time the issue was observed. Clarify whether the problem is missing inventory, evidence waiting for permission to proceed, exclusion, changed content or a stale displayed result. Do not send raw employee evidence or account tokens in a general support conversation.
Large or invalid reads cannot be treated as complete simply because some records were returned. Source capture, evidence recovery and setup review also have different limits and checks. Support should inspect the relevant stage before choosing a retry; a refresh of the display cannot repair a missing source record.
Once an active or scheduled start has been recorded, HiveOrbit retains the proof used for that decision. It continues checking operational prerequisites and current authority, but does not continuously repeat the exact initial completed-day proof as a scoring prerequisite. A later reactivation requires a fresh review. Business owners should still investigate missing or disputed work rather than treat a successful setup decision as permanent evidence of complete source coverage.