Review Piece versions and audit history

How Lead360 helps

Versions and audit gives administrators a history of how a Piece changed, which revision became an immutable version, who performed important actions, and which deployments or consumers use a version. This supports investigation, controlled updates, and accountability.

When to use this workflow

Use Versions and audit before publishing, during incident review, when planning a consumer update, and whenever ownership or behavior is uncertain.

Before you begin

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

• Identify the Piece and relevant time period.
• Collect the consumer, run, or incident evidence that prompted review.
• Know the current expected published version.

Complete the workflow

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

1. Open the Piece and select Versions and audit.
2. Locate the draft revision, published version, deployment, or event in question.
3. Compare identity, capabilities, data, behavior, safety, model, and resource changes.
4. Review actor, timestamp, validation, certification, publish, deployment, and rollback evidence.
5. Record the finding and create a new controlled revision if correction is needed.

Understand the key controls

Revision and version

A revision is editable draft history. A published version is immutable and provides a stable consumer reference.

Audit does not reverse effects

Reviewing or changing Piece configuration does not undo actions already performed by a consumer.

Evidence preservation

Keep relevant version, deployment, Arena, approval, and incident evidence according to operational and legal retention requirements.

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.

• Match live consumers to recorded version identifiers.
• Confirm the selected event belongs to the correct tenant and Piece.
• Document any unexplained gap before making another change.

Troubleshooting

The live version is unclear

Check the consumer or deployment record instead of assuming the most recently published version is active.

A change is not in Piece history

It may belong to the bot, channel, automation, connector, plugin, memory, or consumer configuration rather than the Piece revision.