---
product_area: platform
module: data-job-engine
revision: 1
status: superseded
owned_by: MOD-PFM-DJE
synonyms:
  - result
  - rejection
  - receipt
supersedes: []
id: CON-PFM-DJE-002
name: Record Outcome
feature: FEAT-PFM-DJE-01
product_intent: confirmed
implementation_evidence: observed
source_sha:
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
definition: >-
  Record outcomes are the per-input evidence facet of a data job; this superseded concept retains its
  identifier while active planning uses Data Job.
not_to_be_confused_with:
  - A job state describes overall progress rather than one input record.
  - Destination history belongs to the changed record and serves a different inspection purpose.
facets:
  - name: Applied outcomes
    meaning: 'An eligible operation records its successful result, including unchanged detail where supported.'
    used_for: Inspecting success without assuming every success performed a write.
  - name: Individual refusals
    meaning: 'A refusal records a code, affected fields and safe explanation for one input position.'
    used_for: Preparing corrected input.
  - name: Conflicts
    meaning: Concurrency protection records why a changed destination cannot accept the saved request.
    used_for: Reviewing later edits before another approval.
  - name: Dependency blocks
    meaning: Required references can prevent input from proceeding until another record arrives.
    used_for: Choosing recovery after dependency loading.
  - name: Skipped delivery
    meaning: Producer revision and operation checks can determine that input needs no application.
    used_for: Reconciling recurring deliveries.
  - name: Unattempted work
    meaning: Job interruption can leave input outside completed processing.
    used_for: Accounting for work left undone.
  - name: Committed receipts
    meaning: >-
      Receipt evidence accompanies successful processing and supports deduplication and restoration
      planning.
    used_for: Inspecting committed work and recovery eligibility.
  - name: Refusal-rate protection
    meaning: Aggregate outcomes can hold further processing when input quality is poor.
    used_for: Reviewing unsuitable jobs before more work proceeds.
relationships:
  - to: CON-PFM-DJE-001
    statement: Outcome evidence belongs to its job and input position.
    provenance: documented
    source: 'macroservice-libraries:packages/data-jobs/README.md#What the engine is, in one paragraph'
  - to: CON-PFM-DJE-004
    statement: Rejected keyed creation leaves no producer mapping for its corrected input.
    provenance: documented
    source: 'macroservice-libraries:packages/data-jobs/README.md#Keyed writes and the ID crosswalk'
acted_on_by:
  - CAP-PFM-DJE-003
  - CAP-PFM-DJE-005
  - CAP-PFM-DJE-006
  - CAP-PFM-DJE-007
  - CAP-PFM-DJE-008
  - CAP-PFM-DJE-012
visible_to:
  - ACT-PFM-035
  - ACT-PFM-036
  - ACT-PFM-037
evidence:
  - >-
    Reviewed evidence: macroservice-libraries (54536a44): packages/data-jobs/README.md;
    src/run-data-job-batch.ts, rejection-guard.ts, version-capture.ts, data-job-columns.ts.
  - 'Reviewed evidence: services-crm (a8d1364f): docs/data-jobs.md (What each contact''s outcome can be).'
  - 'Reviewed evidence: services-platform (ad3f6a65): docs/data-jobs/platform-data-operations.md §3.'
---

# Record Outcome

## What It Is

Record outcomes describe what happened to the input of a data job. The first planning draft treated them as a broad concept of their own. This examination folds that explanation into Data Job because an outcome has no independent staff purpose outside the requested operation. This superseded artifact keeps its permanent identity and historical references; active feature and capability declarations use the parent concept.

The distinction still matters when staff inspect work. A job can contain several kinds of result, and its summary alone does not explain every input row. The outcome facet supplies that detail. It gives administrators a way to connect a position in submitted input with an application, refusal or other processing result without creating another domain record for staff to maintain.

## What It Is Not

Outcome evidence does not replace a contact’s version history or an organization’s current values. It describes the job’s handling of input. A job state describes the overall processing phase, while an individual outcome explains one part of that work. These views answer related questions and should not be treated as interchangeable measures of success.

## How It Is Used

Staff inspect the parent job’s result and refusal views when a bulk operation finishes or needs attention. Integrations use the same evidence to decide whether input should be corrected or a missing dependency loaded. Restoration planning uses committed work to assess what can be put back.

The useful question is what follow-up the result calls for. Correcting an invalid value, reviewing another person’s edit and waiting for a parent record are different tasks. Retaining those distinctions helps staff choose the appropriate capability instead of sending every unsuccessful input through the same retry.

## Its Facets

**Applied and skipped input.** These distinguish successful processing from input that did not need another application. Where a domain supports unchanged detail, staff can tell that successful handling did not necessarily create another record revision.

**Refusals and conflicts.** These identify input problems or destination changes that require review. Their safe explanations support follow-up while keeping record values outside the refusal account.

**Dependency blocks and unattempted work.** These explain input waiting for a prerequisite or never reached after interruption. They should not be interpreted as equivalent to malformed input.

**Receipts and aggregate protection.** Committed evidence supports deduplication and restoration assessment. Aggregate outcomes also inform the parent job’s guard against unsuitable input.

## How It Relates

The active home is Data Job. Producer identity mappings help explain duplicate and stale delivery outcomes, while destination history helps restoration planning inspect later changes. Migration runs summarize their child jobs without becoming an alternative ledger for each input record. Those relationships remain useful even though this separate concept is retired.

## What It Could Become

Future result search and server-built exports belong with the job’s inspection capabilities. Product can also improve explanations for unchanged work and restoration exclusions. Any extension should develop the parent’s outcome facet rather than revive a separate concept merely because receipts and refusals have physical storage of their own.