---
schema_version: "1"
id: 82e7399d4ad4753bf7c0af082c4e5cbc47df63f47dd058151792081dc5adafd2
title: Legacy Partner Connect Export, Import, and Update Statuses
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_fix_exp_imp_up_report_statuses.md
canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_fix_exp_imp_up_report_statuses.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f2af88cea954b269958ebb864279b222b93831c1d58dd0da97594289cfd2719e
description: See the outbound and inbound statuses for records that are exported, imported, or updated by using Partner Connect. If you’re a vendor admin, you see export and update issues only (because vendor orgs don’t import data). If you’re a partner admin, you can see import and update issues only (because vendor orgs don’t export data).
products:
  - Sales
  - Slack
  - Cross Cloud
release: "264"
---
# Legacy Partner Connect Export, Import, and Update Statuses

See the outbound and inbound statuses for records that are exported, imported, or updated by using Partner Connect. If you’re a vendor admin, you see export and update issues only (because vendor orgs don’t import data). If you’re a partner admin, you can see import and update issues only (because vendor orgs don’t export data).

## Outbound Statuses: Export and Update

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e43">Status</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e46">What it Means</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e49">Action for Admin to Take</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Duplicate Export Skipped</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The record was skipped because it was previously exported to the partner org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">No further action is necessary.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Exported</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">
              <p>The record was successfully exported. For the data to be successfully delivered to the
                partner org, the partner org must see a corresponding inbound transaction status of
                Imported.</p>
              <p style="margin-bottom:0;">If the vendor admin has elected to send and receive record updates between
                orgs, a connected external record was also created in the partner’s org.</p>
            </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">No further action is necessary.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Exported: Connected Record Create Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The record was successfully exported, but the corresponding connected external record
              failed to be created in the partner’s org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>If the issue occurs once or infrequently, no action is required. In most cases, the
                connected external record is eventually created in the partner org and updated accordingly
                when a vendor user edits an integrated field on the corresponding vendor record, realigning
                the connected records.</p>
              <p>If the issue occurs repeatedly, it indicates a configuration issue.
                Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;">If
                all prerequisites are met, the vendor admin must delete and recreate the field mappings for
                this object. After a vendor deletes and remaps their fields, the partner’s field mappings
                are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Exporting</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The record is in the processing of exporting.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Wait for the export to complete or fail to discern if any further action is necessary.
              </p>
              <p>Exports that remain in progress for more than 60 seconds are no longer attempted, and
                the export is attempted again if a partner user manually retries from the vendor’s
                Experience Cloud partner site.</p>
              <p style="margin-bottom:0;">If the same record continues to fail to move beyond
                the Exporting status, contact Salesforce Customer Support.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: Connection Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed due to a connection authentication issue between the vendor and
              partner orgs. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">Vendor and partner admins must delete their connections and step through the initial
              setup again. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_disconnect_delete.htm&amp;release=264.0.0&amp;type=5" title="If you’re having an issue related to a connection, the vendor or partner admin can delete the connection. After deletion, partner users can no longer export vendor records to the partner org, and updates no longer flow between connected records. Related connection items are also removed from the org depending on which admin initiates the deletion. If admins want to reconnect their orgs, they must step through the end-to-end setup process again. If either admin doesn’t intend to use Partner Connect again in the near term, we recommend turning off the feature.">Delete Connections and Turn Off Legacy Partner Connect</a>.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: External Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed because of an opportunity or lead save error in the partner’s
              org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>The vendor admin must contact the partner admin and ask them to check their email for
                any import issues around the date and time listed in the Last Modified Sent field for this
                transaction. The partner admin can rely on their IT professional for help with interpreting
                any technical descriptions in the csv file attached to the email.</p>
              <p style="margin-bottom:0;">If additional help is
                needed, the partner admin must contact Salesforce Customer Support.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: External Export Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed because Partner Connect encountered an issue with the partner’s
              ability to receive the transaction data from the vendor org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>If the issue occurs once or infrequently, no action is required. If the issue occurs
                repeatedly, the vendor admin must contact the partner admin and ask them to check their
                email for any import issues around the date and time listed in the Last Modified Sent field
                for this transaction. The partner admin can rely on their IT professional for help with
                interpreting any technical descriptions in the csv file attached to the email. </p>
              <p style="margin-bottom:0;">If
                additional help is needed, the partner admin must contact Salesforce Customer
                Support.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: External Field Mapping Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed because Partner Connect encountered an issue with the partner’s
              field mappings for this connection. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;">If all
                prerequisites are met, the vendor admin must delete and recreate the field mappings for
                this object. After a vendor deletes and remaps their fields, the partner’s field mappings
                are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: Internal Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed because of an unknown error in the vendor org. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">If the issue occurs once or infrequently, no action is required. If the issue occurs
              repeatedly, we recommend that the vendor org contacts Salesforce Customer Support.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Not Exported: Internal Field Mapping Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">The export failed because Partner Connect encountered an issue with the vendor’s field
              mappings for this connection. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;">If all
                prerequisites are met, the vendor admin must delete and recreate the field mappings for
                this object. After a vendor deletes and remaps their fields, the partner’s field mappings
                are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: Can’t Find External Record</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update because Partner Connect can’t find the parent lead or
              opportunity record in the external org. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">You must contact the admin at the external org and ask them to check that the
              corresponding parent lead or opportunity record exists, and either admin can contact
              Salesforce Customer Support.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: Connection Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update due to a connection authentication issue occurring in
              your org. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">If the issue occurs once or infrequently, no action is required. If the issue occurs
              repeatedly, vendor and partner admins must delete their connections and step through the
              initial setup again. <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_disconnect_delete.htm&amp;release=264.0.0&amp;type=5" title="If you’re having an issue related to a connection, the vendor or partner admin can delete the connection. After deletion, partner users can no longer export vendor records to the partner org, and updates no longer flow between connected records. Related connection items are also removed from the org depending on which admin initiates the deletion. If admins want to reconnect their orgs, they must step through the end-to-end setup process again. If either admin doesn’t intend to use Partner Connect again in the near term, we recommend turning off the feature.">Delete Connections and Turn Off Legacy Partner Connect</a>.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: External Delivery Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update because Partner Connect encountered an issue with the
              external org’s ability to receive the transaction data you’re sending.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>If the issue occurs once or infrequently, no action is required. If the issue occurs
                repeatedly, you must alert the admin at the external org. Recommend that they check that the
                PRM External Integration User has Create, Read, Update, and Delete access to the platform
                event External Record Share Event (ExtlRecShrEvent). The admin at the external org can rely
                on their IT professional for help.</p>
              <p style="margin-bottom:0;">If the PRM External Integration User has the necessary
                access, we recommend that the admin at the external org contacts Salesforce Customer
                Support.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: External Field Mapping Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update because Partner Connect identified an issue with the
              field mappings for this object in the external org. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;">If all
                prerequisites are met, the vendor admin must delete and recreate the field mappings for
                this object. After a vendor deletes and remaps their fields, the partner’s field mappings
                are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: Internal Field Mapping Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update because Partner Connect identified an issue with your
              field mappings for this object. </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;" dir="ltr">If all prerequisites are met, the vendor admin must delete and recreate the field mappings
                for this object. After a vendor deletes and remaps their fields, the partner’s field
                mappings are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Not Sent: Internal Unknown Error</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org can’t send this update because of an unknown error in your org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">If the issue occurs once or infrequently, no action is required. If the issue occurs
              repeatedly, we recommend that you contact Salesforce Customer Support.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Sending</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org is in the process of sending an update.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">
              <p>Wait for the update to complete or fail to discern if any further action is necessary.
              </p>
              <p>Most updates that remain in the Update Sending status eventually resolve the next time
                one of your users edits an integrated field on the same record, and both the missed and new
                updates are saved to the corresponding connected record in the external org at the same
                time.</p>
              <p style="margin-bottom:0;">You or another user in your org can check whether the issue resolves
                automatically by attempting another update on the record and running the report
                again.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e43 ">Update Sent</td>

            <td data-label="What it Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e46 ">Your org sent a record update to the external org. For the update to be successfully
              delivered to the external org, the external org must see a corresponding inbound transaction
              status of Update Received.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e49 ">No further action is necessary.</td>

          </tr>
        </tbody>
      </table>

## Inbound Statuses: Import and Update

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e376">Status</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e379">What It Means</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d9856e382">Action for Admin to Take</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Imported</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">
              <p>The record was successfully imported.</p>
              <p style="margin-bottom:0;">If the vendor admin has elected to send and
                receive record updates between orgs, a connected external record was also created in the
                partner’s org.</p>
            </td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">No further action is necessary.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Imported: Save Error on Connected External Record</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">The record was successfully imported, but the corresponding connected external record
              failed to be saved in the partner’s org.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">
              <p>If the issue occurs once or infrequently, no action is required. In most cases, the
                connected external record is eventually created in the partner org and updated accordingly
                when a vendor user edits an integrated field on the corresponding vendor record, realigning
                the connected records.</p>
              <p style="margin-bottom:0;">If the issue occurs repeatedly, we recommend that you contact
                Salesforce Customer Support.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Update Not Received: Field Mapping Error</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">Your org can’t receive this update because Partner Connect can’t map the external
              org’s field mappings to your field mappings.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">
              <p>Vendor and partner admins can verify that they followed the prerequisites for field
                mapping. See <a href="https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_prereq_mapping_plan.htm&amp;release=264.0.0&amp;type=5" title="To avoid revisiting your Partner Connect setup, we recommend that vendors and partners meet to agree on a clear plan for integrating objects and fields across Salesforce orgs. Vendor admins kick off planning by creating a list of the items they want to integrate into the partner’s org. Sometimes admins from either org are required to customize their Lead or Opportunity objects to integrate records smoothly.">Planning Object and Field Integration for Legacy Partner Connect</a>.</p>
              <p style="margin-bottom:0;">If all
                prerequisites are met, the vendor admin must delete and recreate the field mappings for
                this object. After a vendor deletes and remaps their fields, the partner’s field mappings
                are also removed, and the partner must also remap their fields.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Update Not Received: Save Error on Connected External Record</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">Your org can’t receive this update because the corresponding connected external record
              failed to save the changes.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">
              <p>If the issue occurs once or infrequently, no action is required. In most cases,
                updates that were missed are sent the next time a user in the external org updates an
                integrated field on the same record. Both the missed and new updates are saved to the
                corresponding connected record in your org at the same time.</p>
              <p>If the issue occurs
                repeatedly, compare the connected external object for this record and verify that you
                configured each field to exactly match the corresponding field on the parent object (lead
                or opportunity).</p>
              <p style="margin-bottom:0;">You could also get more information by having a partner user attempt
                to export a different but similar record as a test. If you’re able to trigger the same
                issue, the resulting import notification email sent to the partner admin includes a
                detailed error message in the attached csv file.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Update Not Received: Unknown Error</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">Your org can’t send this update because of an unknown error.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">If the issue occurs once or infrequently, no action is required. If the issue occurs
              repeatedly, we recommend that you contact Salesforce Customer Support.</td>

          </tr>
          <tr class="">
            <td data-label="Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e376 ">Update Received</td>

            <td data-label="What It Means" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e379 ">Your org received a record update sent from the external org and saved it to the
              corresponding connected external record.</td>

            <td data-label="Action for Admin to Take" class="slds-cell-wrap" style="vertical-align:top;" headers="d9856e382 ">No further action is necessary.</td>

          </tr>
        </tbody>
      </table>

#### See Also

- [Build and Run a Legacy Partner Connect Status Report](https://help.salesforce.com/s/articleView?id=slack.prm_pc_fix_exp_imp_up_report.htm&release=264.0.0&type=5 "Vendor and partner admins can build a report to see the status of the export, import, and update transactions sent between orgs. Doing so lets admins address recurring issues, such as failed exports, imports, or updates.")
- [Assess Export, Import, and Update Issues With a Legacy Partner Connect Status Report](https://help.salesforce.com/s/articleView?id=slack.prm_pc_fix_exp_imp_up_report_assess.htm&release=264.0.0&type=5 "Vendor and partner admins can diagnose recurring export, import, and update issues by building Partner Connect status reports and working together to interpret the issues.")