Roll back a Piece deployment

How Lead360 helps

Piece rollback provides a controlled recovery path when a newer deployed version causes a verified problem. It moves the supported deployment or consumer reference to an earlier immutable version while preserving the newer version, audit evidence, and effects that already occurred.

When to use this workflow

Use rollback when a live issue is linked to a Piece version and restoring a known compatible version is safer than preparing an immediate new revision.

Before you begin

Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.

• Confirm the incident and affected consumers.
• Identify the prior compatible published version.
• Review schema, capability, memory, resource, and consumer compatibility.

Complete the workflow

Follow the steps in order and stop when a required resource, permission, review, or approval is missing.

1. Pause or contain affected channels and workflows when needed.
2. Open the Piece deployment or supported consumer history.
3. Select the known compatible prior version and review rollback impact.
4. Approve and perform the rollback through the supported control.
5. Test the restored consumer and continue incident review for effects already completed.

Understand the key controls

No history rewrite

Rollback changes the active reference where supported. It does not delete the newer immutable version or audit history.

Completed effects

Messages sent, records changed, payments, publications, and other past effects are not undone by changing the Piece version.

Compatibility

A prior Piece may not fit newer consumer inputs or resources. Review compatibility before rollback.

Confirm the result

Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.

• Confirm the consumer reports the intended prior version.
• Retest critical workflows through the real surface.
• Review and remediate completed effects separately.

Troubleshooting

The prior version cannot be selected

It may be incompatible, unavailable to that consumer, or outside the supported deployment path. Use a new corrective revision when needed.

Rollback did not fix the issue

Investigate channels, resources, connectors, plugins, automations, memory, model availability, and provider state rather than assuming the Piece was the only cause.