Troubleshooting Scenario Questions

The Connected App callback URL and OAuth scopes

Why wrong: Connected Apps are used for Salesforce-to-Salesforce or internal API integrations, not AWS S3 bucket credentials.

The Marketing Cloud Connector user profile settings

Why wrong: Marketing Cloud Connector settings are irrelevant to AWS S3 storage integrations.

The Einstein Trust Layer activation guardrails

Why wrong: Einstein Trust Layer governs generative AI interactions and has no role in S3 export authentication.

The Einstein Studio model training metrics.

Why wrong: Einstein Studio metrics evaluate machine learning model accuracy, not activation job status.

The Salesforce Core Setup Audit Trail.

Why wrong: Salesforce Core Audit Trail tracks CRM setup changes, not Data Cloud activation publish pipelines.

The Marketing Cloud Journey Builder analytics dashboard.

Why wrong: Journey Builder tracks messaging performance, not Data Cloud backend publishing pipelines.

Rewrite the Identity Resolution ruleset to use a fuzzy match rule instead of exact match for email.

Why wrong: Fuzzy matching handles typographical errors, but case normalization is best handled via formulas or exact match rules configured with standardized casing.

Increase the Match Confidence threshold to 100%.

Why wrong: Increasing match confidence does not solve case sensitivity issues in exact match rules.

Recreate the Data Space to reset the ruleset index.

Why wrong: Recreating the Data Space is unnecessary and does not fix data formatting inconsistencies.

Marketing Cloud Engagement requires Real-Time Data Graph activation for all Calculated Insights.

Why wrong: Real-Time Data Graph is used for streaming unified profiles, not as a strict prerequisite for batch Calculated Insights activation.

Calculated Insights cannot be exported to Marketing Cloud Engagement due to API limits.

Why wrong: Calculated Insights are routinely used for activation in Marketing Cloud Engagement via standard publishing mechanisms.

Activation targets only support streaming data streams, not batch-based Calculated Insights.

Why wrong: Activation targets can consume batch data, provided the Calculated Insight outputs are correctly mapped to activation-enabled DMOs.

Einstein Trust Layer generative AI moderation guardrails.

Why wrong: Einstein Trust Layer governs AI prompts and responses, not cloud file storage exports.

Salesforce Core CRM Profile object sharing rules.

Why wrong: Core CRM sharing rules do not apply to Data Cloud cloud storage exports.

Marketing Cloud Engagement API connection scopes and OAuth credentials.

Why wrong: Marketing Cloud credentials are irrelevant to Cloud File Storage targets.

Recreate the Identity Resolution ruleset to clear transaction locks.

Why wrong: Identity resolution has no impact on webhook endpoint response timeouts.

Increase the Data Cloud activation target chunk size to 1 million records per request.

Why wrong: Increasing payload size will worsen timeout issues by increasing processing time per request.

Switch the activation target type from webhook to cloud storage.

Why wrong: Changing target types changes the architecture entirely rather than troubleshooting the webhook timeout.

Configuring an activation target with an invalid webhook URL.

Why wrong: Activation targets are completely separate from Calculated Insight compilation.

Failing to enable Salesforce Shield Platform Encryption on the user profile.

Why wrong: Shield encryption status does not cause Calculated Insight SQL compilation failures.

Check the Salesforce Core Setup Audit Trail for login failure events.

Why wrong: Core setup audit trail does not track row-level activation export errors.

Open the Marketing Cloud Engagement Tracking Report for email sends.

Why wrong: Tracking reports evaluate email engagement, not Data Cloud export failures.

Examine the Data Stream Ingestion status dashboard for failed CSV files.

Why wrong: Ingestion dashboards monitor source data loading, not activation export errors.

Ensure that the segment uses an append-only publishing policy.

Why wrong: Append-only policies would prevent updates by design, but standard updates require correct upsert keys.

Increase the batch size of the Data Stream ingestion job.

Why wrong: Data stream batch size does not impact activation export logic.

Check if the Marketing Cloud connector user has View All permissions on the Contact object.

Why wrong: Marketing Cloud data extension updates are managed via API integrations, not CRM object FLS.

Increase the activation target polling frequency.

Why wrong: Activation targets do not affect identity resolution matching output.

Delete all data spaces and reinstall the Data Cloud package.

Why wrong: Reinstalling packages is unnecessary and destructive.

Modify the Apex controller class in Sales Cloud to trigger the API push.

Why wrong: Ingestion API operates independently via REST endpoints and does not require Sales Cloud Apex controllers.

Update the Identity Resolution match rules to resolve duplicate source records.

Why wrong: Identity Resolution occurs downstream after ingestion; failing ingestion prevents records from reaching DLOs in the first place.

Switch all reconciliation rules from Source Sequence to Longest String.

Why wrong: Reconciliation rules govern field survivorship, not profile linking counts.

Delete all data spaces and restart the entire Salesforce CRM instance.

Why wrong: Restarting the CRM instance is destructive and unnecessary.

Reconciliation rules were set to Most Recent instead of Source Sequence.

Why wrong: Reconciliation rules determine survivorship after records are linked, not whether matching occurs.

Data Cloud requires manual SQL triggers to activate e-commerce data streams.

Why wrong: Data streams run automatically upon ingestion configuration.

The Unified Individual DMO is missing an activation target assignment.

Why wrong: Activation targets have no impact on the identity resolution matching engine.

Increase data stream ingestion frequency from hourly to real-time.

Why wrong: Increasing ingestion frequency would increase the workload and worsen timeout issues.

Restart the core Salesforce CRM production server.

Why wrong: Restarting CRM servers has no impact on Data Cloud background execution jobs.

Switch the reconciliation rule to Highest Frequency.

Why wrong: Reconciliation rules execute after matching; they do not resolve matching phase timeout exceptions.

Unix Epoch timestamp integer (e.g., 1698000000)

Why wrong: Unix epoch integers are not standard for Data Cloud timestamp fields without conversion formulas.

RFC 2822 email date format

Why wrong: RFC 2822 is not supported natively.

US Standard format (MM/DD/YYYY HH:MM AM/PM)

Why wrong: US regional formats cause parsing failures.