Loading

Salesforce Enforces New Security Requirements in Summer 2026

Journeys and Automations in Marketing Cloud Engagement

Data View: Reconcilable Disposition

You are here:

Data View: Reconcilable Disposition

To view reconciliation disposition data for emails sent from your account, query the _ReconcilableDispositionView data view in Automation Studio. Data is retained for seven days.

Columns

Name	Description	Data Type	Data Extension Data Type	Nullable
JobId	Unique identifier for the job.	NVARCHAR(100)	Text	No
Channel	Channel Identifier 0 - Email 1 - SMS 3 - Omni 4 - Push	BYTE	Number	No
Disposition	Disposition status for the subscriber. 1 - Sent. Indicates that Marketing Cloud Engagement successfully handed the message off to the mail servers. It doesn't indicate inbox delivery or email address validation. 2 - NotSent. Indicates that the message failed to hand off to the delivery system. This status applies to messages that expired in the queue or encountered an internal system failure.	BYTE	Number	No
MessageKey	Message key used to reconcile message disposition from Marketing Cloud Engagement with external systems.	NVARCHAR(100)	Text	No
SubscriberKey	Key that uniquely identifies the recipient within the MID.	NVARCHAR(100)	Text	Yes
SubscriberId	Unique subscriber ID for the recipient. This value can be NULL if the intended subscriber was invalid.	BIGINT	Number	Yes
ErrorCodeId	Error code ID returned when the message wasn’t sent to the subscriber.	INT		Yes
ExpirationTime	Timestamp when the message is considered expired by the system.	DATETIME		No
ErrorName	The name of the error returned when the message wasn’t sent to the subscriber.	NVARCHAR(256)		No
StartTime	Timestamp when processing of the message began. For data extension-based sends, this value represents when the job was originally scheduled to start. For LLTS-based sends, this value represents when the API received the message.	DATETIME

Did this article solve your issue?

Let us know so we can improve!

Loading

Salesforce Help | Article