Skip to main content
Version: 2026.09

How Revisions Work

A Resource keeps one Resource ID for its whole life. Each change adds a revision with its own Revision ID.

Image to add

A timeline for one Resource ID with three revisions: Revision A (first upload), Revision B (new upload), and Revision C (connect update), each with its own Revision ID.
static/img/training/revision-timeline.png

Caption: One Resource ID, and a new Revision ID for each revision.

  • Revisions can’t be changed. A new upload or connection adds a revision, and earlier revisions are never overwritten.
  • To view an earlier revision, select it under Resource Versions.
  • Version and revision mean the same thing.

What creates a new revision?​

  • You upload a new file. Add a version and choose a file.
  • The source changes. Add a version from the Connect tab to point at the updated file in the app.
  • A job writes back. Some functions update the file in the third-party app, and the platform records a new revision of the same Resource.
  • A partner updates it. New revisions sync in over a Secure Connection and are marked with the connection they came from.

Connected Resources are versioned the same way as uploaded ones.

Later in the course you’ll see two more ideas: a System can follow the latest revision of a Resource or stay on a specific one, and running a job on a revision creates artifact revisions.

Learn more: Version control.