From content history page

Connect Cloud records a revision each time your content is published or republished. The content history page lists every revision, shows exactly what was deployed each time, and lets you download the source for a given revision.

Open it by clicking the History icon in the header of your content admin page.

Revision list

Revisions are listed newest first. Each entry shows the revision number, the date and time it was created, and an icon indicating its publish status:

  • A green checkmark means the revision published successfully.
  • A red warning icon means the revision failed to publish.
  • A clock means publishing is still in progress.

Revision numbers increase over time, so the highest number is the most recent deployment.

Select any revision to view its details.

Revision details

The details pane opens with the publish status of the selected revision, followed by the recorded build information grouped into four categories:

Source

  • Source code - the repository the revision was published from
  • Commit - the commit the revision was built from, linked to the commit on GitHub
  • Primary file - the entrypoint file for the content
  • Framework - the data framework the content was published as

Software versions

  • The Python, Quarto, and R versions used to build the revision

Compute

  • Memory and CPU allocated to the revision

Publish time

  • Start time - when publishing began
  • Duration - how long publishing took

Details that were not recorded or do not apply to a given revision display N/A. For example, content published from your IDE or terminal has no repository or commit, so those fields show N/A.

Download source

Click Source in the revision header to download a .zip archive of the source code for that revision. The archive is named after your content title and revision number.

Downloading source requires permission to edit the content, so it is not available to viewers of your content. If a revision’s source was never stored (e.g. if the revision’s source references a GitHub repository Connect Cloud does not have access to), the button is disabled and shows No source available.

This is useful for recovering the exact code behind a deployment - particularly for content published from your IDE or console or terminal, where the source is not stored in a repository.

You can also download source from the Info panel of the content admin page and from the More actions menu on your Home page. Both download the current revision.

Logs

The bottom of the details pane shows the logs captured for the selected revision. This is the fastest way to diagnose a revision that failed to publish.