---
title: "Pull Salesforce updates for Jira issues in bulk"
canonical: "https://support.appfire.com/space/477986818/3442049074/Pull%20Salesforce%20updates%20for%20Jira%20issues%20in%20bulk"
format: markdown
---
> ⚠️ - JQL search in **Bulk Operations** returns only associated Jira issues.
> ⚠️ - The ORDER BY operation does not work in the **Bulk Operations** JQL search.

## Partial failure of Bulk Pull


## Salesforce API limits and Bulk Pull

### What to expect in Bulk Operations

When you open **Bulk Operations**, Connector for Salesforce & Jira checks your Salesforce API usage when possible and may show one of the following:

| **Status** | **When it appears** | **What it means** |
| --- | --- | --- |
| **Salesforce API usage is high** | Less than 20% of your daily API quota remains | You can still run bulk pull, but you should review the number of issues in your search results before continuing. |
| **Bulk operations unavailable** | Less than 10% of your daily API quota remains | **Bulk Pull** and **Bulk Push** are temporarily disabled to help avoid exhausting your remaining API requests. They become available again as your quota recovers. |

When usage information is shown, it appears in the form: **Remaining API requests: X of Y (Z% remaining)**.

### Recommendations

- Start with a narrow JQL query and confirm the results before pulling a large set of issues.
- Avoid very large bulk pulls when your Salesforce org is already close to its API limit.
- Plan around peak usage in Salesforce and other integrations that share the same API quota.
- Monitor failures after a bulk pull. If Salesforce returns API limit errors, wait for your quota to recover and retry with a smaller batch.

## Related pages

- [Push updates for multiple Jira issues in bulk mode](https://support.appfire.com/space/477986818/2560558881/Push+updates+for+multiple+Jira+Issues+in+bulk+mode)
- [Configure connection settings](https://support.appfire.com/space/477986818/2560917543/Configure+connection+settings)