--- title: "Auto-Push/Pull Fails While Manual Sync Succeeds" canonical: "https://support.appfire.com/space/SUPPORT/3107258691/Auto-Push%2FPull%20Fails%20While%20Manual%20Sync%20Succeeds" format: markdown --- > Macro (toc) # Environment - **Product:** Connector for Salesforce & Jira - **Platform:** Jira Cloud - **Salesforce Environment:** All supported editions # Overview This article helps identify and resolve cases where automatic synchronization from Salesforce to Jira fails while manual synchronization continues to work. This typically occurs when a Salesforce field referenced in a mapping has been deleted, renamed, moved, or is otherwise invalid. In some cases, Jira and Salesforce do not display a visible error to users; the backend error can only be confirmed by Appfire Support in CloudWatch logs. # Problem Users may experience a situation where updates made in Salesforce are not automatically reflected in Jira issues (auto-push fails), despite manual "Pull" operations from the Jira UI working correctly. ### Symptoms include: - Auto-sync from Salesforce to Jira stops working, often after Salesforce schema or mapping changes such as field renames, deleted fields, or mapping updates. - Manual push and pull operations still work as expected. - No visible UI or pop-up errors appear in Jira or Salesforce, and HAR files do not show an error. - The managed package method `JCFS.API.pushUpdatesToJira()` was initiated but failed to proceed. - Appfire Support may confirm the issue in CloudWatch logs with a backend error similar to the following: ``` No such column 'field_name__c' on entity 'Object_Name__c'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name.. Please reference your WSDL or the describe call for the appropriate names. ``` # Cause The root cause is an invalid Salesforce field referenced by one or more connector field mappings. Because Salesforce rejects the entire SOQL query when any referenced field is invalid, a single broken field mapping can prevent automatic synchronization for all records using that Salesforce object on the connection. This issue may not produce a visible error in Jira or Salesforce. If the invalid field cannot be identified from the configuration steps below, contact Appfire Support so an agent can review the backend CloudWatch logs and confirm the exact Salesforce field causing the failure. > ℹ️ **CloudWatch log location for Appfire Support:** Search the `sfjc-production` log group for the Salesforce object and invalid field shown in the backend error, such as `No such column`, `Scenario__c`, or the field API name. These logs are not visible in the customer UI, which is why the issue can appear as a silent auto-sync failure. ### Why manual pull works but auto-push fails **Manual Pull:** When you perform a manual pull from a specific Jira issue, the connector only requests the Salesforce fields mapped for that specific Jira project and issue type. **Automatic Sync:** When Salesforce triggers an automatic update (via `/api/events`), the connector loads the Salesforce record using a combined set of all fields mapped to that Salesforce object across every Jira project sharing that connection. If a single mapping exists—even in an unrelated or inactive project—that references a non-existent or renamed Salesforce field (for example, `lead_Retex__c`), the entire SOQL query fails, preventing the automatic sync from completing. > ℹ️ **Important:** Automatic synchronization evaluates all Salesforce field mappings for the object across the entire connection. A broken mapping in another Jira project or issue type can prevent automatic synchronization even when the affected Jira issue does not use that mapping. ### Example Project A maps: ``` Scenario__c → Customer_Name__c ``` Project B maps: ``` Scenario__c → lead_Retex__c ``` If `lead_Retex__c` is deleted or renamed in Salesforce, automatic synchronization may fail for both projects because the connector loads all mapped `Scenario__c` fields across the connection during automatic sync. # Solution / Workaround Follow these steps to identify and resolve the invalid mapping. ### 1. Verify the Field in Salesforce 1. Log in to your Salesforce organization. 2. Navigate to **Object Manager** and select the object mentioned in the error (for example, `Scenario__c` or `Case`). 3. Go to **Fields & Relationships** and search for the API name flagged in the logs (for example, `lead_Retex__c`). 4. Confirm whether the field: - Exists - Has been renamed - Was deleted - Belongs to a different Salesforce object than the one referenced in the error If necessary, use Salesforce Workbench's **Describe** functionality or another schema inspection tool to verify the exact API name of the field. ### 2. Audit Connector Field Mappings 1. In Jira, navigate to **Apps → Connector for Salesforce → Bindings → Mapping**. 2. In the top-right corner, export a JSON file containing all mappings for the project. 3. Search the exported JSON for the invalid field name identified in Step 1. Use **Ctrl+F** to find the field reported in the error. 4. Because automatic synchronization aggregates mappings, repeat this audit for **every bound Jira project associated with the connection**. ### 3. Correct or Remove the Mapping - If the field was renamed, update the mapping to use the correct Salesforce API name. - If the field was deleted, remove the mapping entirely from the configuration. - If the mapping is not visible in the UI, delete it directly from the exported JSON file and re-import the updated file. - **Important:** Always keep a backup of the original exported file before making changes. - If the field belongs to another Salesforce object, correct the mapping to reference the appropriate field on the correct object. > **Note:** Ensure you perform this check across all projects and issue types that use the object in question. If Salesforce reports additional invalid columns after correcting the first field, repeat the audit process until all invalid field references have been removed. ### 4. Verify Connection Settings Ensure that **Automatic Pull from Salesforce** is enabled in your connection settings. In Jira → Settings → Apps → Connector for Salesforce → Connection → Configure ![image-20260616-190943.png](media://9db79aca-6c2a-4afb-bfc1-787cbb7ed939) Also verify that the Salesforce integration user has the necessary permissions. Salesforce Administrator and Jira Administrator permissions are recommended during setup and troubleshooting. ### 5. Validate the Fix After correcting the mapping: 1. Update a Salesforce record associated with Jira. 2. Allow the automatic synchronization process to run. 3. Verify that the linked Jira issue updates successfully. 4. If Salesforce reports another invalid field, repeat the mapping audit process and correct any remaining invalid mappings. Once all invalid mappings have been removed or corrected, the automatic sync process will be able to successfully query Salesforce, and updates should resume flowing to Jira.