---
title: "Attachment Deletion Behavior in Salesforce Jira Connector"
canonical: "https://support.appfire.com/space/SUPPORT/3531341836/Attachment%20Deletion%20Behavior%20in%20Salesforce%20Jira%20Connector"
format: markdown
---
> Macro (toc)

## Environment

**Product:** Connector for Salesforce and Jira  
**Environment:** Cloud and Data Center

## Overview

This article explains how attachment deletions are handled when synchronizing the **Connector for Salesforce and Jira** between Jira Cloud and Salesforce.

## Problem

### Observed behavior

- **Deletions are not synchronized:** Deleting an attachment in Jira does not delete it from Salesforce, and deleting it in Salesforce does not delete it from Jira.
- **Attachments are matched by file name:** During synchronization, the connector checks the attachment name. If the file still exists in one system, it can be recreated in the other system after deletion.
- **Automatic synchronization can restore files quickly:** Auto Push, Auto Pull, or configured triggers can start synchronization soon after an attachment is deleted.
- **Synchronization limits apply:** Each synchronization session supports up to 50 attachments and 700 MB total. Salesforce-to-Jira synchronization supports files up to 350 MB each.

## Cause

Attachment deletions are not propagated between Jira Cloud and Salesforce. During synchronization, the connector matches attachments by file name, so an attachment that remains in one system can be recreated in the other. Automatic synchronization can therefore restore a deleted attachment shortly after it is removed.

## Solution/Workaround

To permanently remove an attachment, delete it manually from both Jira and Salesforce. Temporarily pause synchronization before deleting the file, and resume it only after confirming that it has been removed from both systems.

### Procedure

1. Identify the exact attachment to remove, including its file name, and note the Jira issue and Salesforce record where it is currently stored.
2. Temporarily pause all synchronization processes that could copy the attachment again.
3. Delete the attachment from the Jira issue.
4. Delete the attachment with the same file name from the corresponding Salesforce record. If multiple files have similar names, confirm the file details before deleting to avoid removing the wrong attachment.
5. Refresh both records and verify that the attachment is no longer listed or downloadable in Jira and Salesforce.
6. Resume synchronization only after the attachment has been removed from both systems. If synchronization is resumed while the file remains in either system, the connector may recreate it in the other system.
7. Run or monitor the next synchronization and verify that the deleted attachment does not reappear. If it returns, pause synchronization again and check for another copy of the file or an automation that is triggering synchronization.

## Related documentation

- [Work with attachments](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1754432218) — General overview and configuration.
- [Work with attachments in Jira](https://appfire.atlassian.net/servicedesk/customer/portal/11/article/3092024038) — Attachment push and pull mechanisms.
- [Connector for Salesforce and Jira changes](https://appfire.atlassian.net/servicedesk/customer/portal/11/article/3091956863) — Attachment limits and product changes.