Salesforce Load component fails with authentication error

Expired or invalid Salesforce credentials in the Matillion connection profile

Update the Salesforce authentication credentials in the Matillion connection settings. Verify the org type (production or sandbox) matches the target environment.

Transformation pipeline produces null values for mapped fields

Calculator component expressions reference field names that do not exist in the source object

Open the Calculator component and verify each expression maps to a valid source field. Check for renamed or deprecated fields in the Salesforce schema.

SQL Script component fails during stored procedure execution

Target Snowflake table does not exist or the table schema has changed

Verify the Snowflake table name matches the Table Output component configuration. Run the table creation script if the table is missing.

Records appear in staging but do not reach production

Staging Review is enabled, and records are waiting for manual review in Data Foundry

Check the Matching Data Review page for flagged records. Approve valid records to release them to production.

Full sync pipeline runs but no records appear in Snowflake

The IO_DATA_SOURCE expression in the Calculator component contains an incorrect data connector UUID

Verify the UUID matches the Salesforce Data Connector identifier. Retrieve the correct UUID from the data connector configuration page.

Scheduled job does not run at the expected interval

The start date is set in the future, or the schedule interval was not saved correctly

Open the job detail page and verify the start date, time, and interval settings. Click Edit Job to correct any misconfigured values, then click Save .

Scheduled job runs but imports zero records

The linked data source has no new records, or the data connector configuration is invalid

Verify the data connector connection settings on the Import Sources tab. Run a manual import to confirm the source returns records.

Scheduled job completes with validation errors

Imported records fail field-level validation rules defined in the staging environment

Check the validation error details on the job result page. Correct the source data or adjust validation rules to accommodate valid edge cases.

Too many records flagged as duplicates (false positives)

Matching rule criteria are too broad: the comparison field matches on partial or common values

Narrow the matching criteria by adding additional comparison fields or switching to exact-match logic. Test the rule against a sample dataset before activating it on production data.

Duplicate records bypass the matching rule and reach production

The matching rule is inactive, or Staging Review is disabled for the target object

Navigate to Data Foundry and verify the rule status is Active. Confirm that Staging Review is enabled for the relevant object.

Pre-configured matching rule does not appear after enabling Staging Review

The event handler that creates the rule did not fire, or an error occurred during rule creation

Disable and re-enable Staging Review for the object. If the rule still does not appear, create a matching rule manually using the same criteria documented in the pre-configured rules reference.

Campaign generates fewer work orders than expected

Asset filter criteria are too restrictive, excluding assets that should be targeted

Review the campaign's asset criteria. Broaden the filter conditions and preview the matching asset count before relaunching the campaign.

Revenue Campaign option is unavailable during campaign creation

Opportunities are not enabled in the PTC Orbit configuration

Contact the administrator to enable Opportunities in the organization's PTC Orbit configuration settings.

IoT alerts do not appear on the Pending Items page

The asset does not have an active IoT sensor feed, or the sensor integration is not configured

Verify the asset has a connected sensor and the IoT integration is active. Check the integration endpoint configuration in the reference documentation.

Pending items accumulate without linked work orders

Maintenance team members are not triaging the Pending Items page regularly

Establish a triage schedule for the Pending Items page. Set a default admin preset view filtered by priority to surface high-urgency alerts first.

Maintenance data pipeline fails with a Salesforce authentication error

The Salesforce credential configuration in PTC Orbit is invalid or expired

Open Settings and verify the Salesforce authentication credentials. Confirm the connected org type matches your ServiceMax Core environment. Reconfigure the credentials; see Configuring Salesforce Authentication.

PM objects (PM Plan, PM Coverage, PM Schedule) do not appear in Snowflake after pipeline execution

The maintenance data pipeline was not configured with the correct object mappings, or the Matillion job did not include all required PM objects

Open the Matillion project and verify the maintenance pipeline configuration includes all six PM objects. Rerun the pipeline after correcting the object list. See Configuring the Maintenance Data Pipeline.

Maintenance Performance Dashboard displays empty or incomplete data

The maintenance data pipeline has not run, or PM objects failed to load into the canonical data model

Verify that the maintenance data pipeline completed without errors in Matillion. Check the Snowflake tables for the expected PM object records. Rerun the pipeline if records are missing.