---
title: "Records with an Unknown Outcome"
description: "SAP did not confirm a change in time, so it may or may not have been applied; MDM never sends such a record again by itself."
source: "https://help.rikaiso.com/public-cloud/2026.2/outcome-unknown"
edition: "public-cloud"
editionLabel: "S/4HANA Public Cloud"
version: "2026.2"
latest: true
language: "en"
section: "Working with Master Data > Processing Records into SAP"
updated: "2026-11-05"
---

# Records with an Unknown Outcome

> SAP did not confirm a change in time, so it may or may not have been applied; MDM never sends such a record again by itself.

> **Draft brief for authors.** Replace with the final text; keep the concept-page structure.

**Page type:** Concept · **Audience:** Processor

**Contains:** what "Outcome unknown" means (a timeout, a lost connection, a status that could not be saved after SAP answered); why MDM never resends it by itself (a create or an operation could be applied twice); what to do: check the record in SAP (the link), then either remove the record from the Task or send it again with Retry All; how the history shows it.

**Related information:** `retrying-failed-records`, `concept-safety-rules`, `opening-records-in-sap`.

**Source in the product repository:** `.claude/rules/mass-processing.md` "Never twice" (D42).