Bulk operation partially failed
What’s happening
Section titled “What’s happening”A bulk operation completed for some records but encountered errors on others. A notification appeared saying something like “Bulk operation partially failed — {N} updated, {F} failed.”
Partially completed bulk operations aren’t automatically rolled back. The records that were already updated keep the change. You need to decide whether to roll back the completed changes, manually fix the failed records, or re-run a targeted operation on just the failed ones.
How to fix it
Section titled “How to fix it”Step 1: Review what happened
Section titled “Step 1: Review what happened”- Go to Settings in the left sidebar.
- Select Recent bulk operations.
- Find the partially failed operation and select it to see the details.
- The details show which records succeeded and which failed, along with a reason for each failure.
Step 2: Decide on your approach
Section titled “Step 2: Decide on your approach”Option A: Roll back the entire operation
If the partial result is worse than the starting state (for example, you added a tag to some members but not others, and an incomplete tag assignment is misleading):
- On the Recent bulk operations page, select Rollback next to the operation.
- Confirm the rollback in the dialog.
- The completed changes are reversed. A “Bulk operation rolled back” confirmation appears.
The rollback window is 48 hours. After that, the Rollback option is no longer available.
Option B: Fix the failed records manually
If the successful changes are correct and you only need to address the failed ones:
- Note which records failed from the details view.
- Open each failed record and make the change manually.
- If the failure reason suggests a systemic issue (see below), fix that first.
Option C: Re-run on just the failed records
If the failures were due to a temporary problem (like a network interruption):
- In the member list, filter or search to find only the failed records.
- Select them and run the same operation again.
Common failure reasons and what to do
Section titled “Common failure reasons and what to do”| Failure reason | What to do |
|---|---|
| “Archived with active subscription” | Cancel the subscription first, then re-run the operation on that member. |
| “Already has this tag” | No action needed — the record already had the tag you tried to add. |
| “Modified since preview” | Another admin changed the record between the preview and the commit. Review the record and re-run if still needed. |
| “Cannot modify cancelled membership” | Cancellation is a terminal state for some operations. Review whether the intended change is appropriate for a cancelled member. |
| “Insufficient permissions” | Your role may not cover all the records in the selection. Contact your org owner. |
If that didn’t work
Section titled “If that didn’t work”- The Rollback option is greyed out or absent — the 48-hour rollback window has expired. You can’t roll back through MapleGather. Contact support if you need help reversing the changes.
- The details don’t show which records failed — try reloading the Recent bulk operations page. If the details still don’t appear, contact support with the date and time of the operation.