☁️ Loving our new documentation website? Provide feedback in the CloudCannon Community! ✨

Changelog

Subscribe with RSS to keep up with the latest changes.

Table of contents

503 Error Postmortem#

Over the past week, we experienced a significant increase in bot and crawler traffic. This exposed a weakness in how our application managed database connections, leading to 503 errors for Sites hosted on CloudCannon. We take reliability seriously, and would like to apologize to all customers affected by this incident.

We have deployed a series of changes to address the root cause of this issue and are actively monitoring our hosting. We will confirm the effectiveness of these changes over the coming days. We are also working on broader architectural improvements to provide additional resilience under high traffic conditions. For the full incident postmortem, please see our Status page.

This release also addressed several issues, including those affecting new payment methods, resolving Syncing Errors, and custom Testing Domains for Client Organizations.

Fixes

  • Fixed an issue where, in some cases, you could not retry a payment after a failed payment.
  • Fixed an issue where, in some cases, the Reconnect or Clear and Reconnect buttons for resolving Syncing Errors did not work.
  • Fixed an issue preventing Partner Organizations from creating custom Testing Domains for their Client Organizations.

Fixed 503 Errors#

This release addressed 503 errors on Sites hosted through CloudCannon.

Fixes

  • Fixed an issue causing 503 errors for several Sites hosted on CloudCannon.

Improved Schema reliability#

This release improved the reliability of Schemas when creating new files and loading existing files in the Data Editor, and added more controls to the Bandwidth graphs on the Org Home and Site Dashboard pages.

It also addressed several issues, including those affecting Hugo shortcodes, filtering in the Collection Browser.

Features & Improvements

  • Updated Schema files to use unsaved content from your current editing session. Previously, Schemas used the last saved version of the file, which meant changes to a Schema file would not take effect until after saving.
  • Added more controls to the Bandwidth graph under the Usage tab for the Org Home and Site Dashboard pages. You can now select a custom date ranges, group the Bandwidth table by Site (Org Home only), and load more records on the Bandwidth table.

Fixes

  • Fixed an issue where CloudCanon would fail to load Schema files and Default content files with Markdown extensions (.md) if the front matter block was missing its closing --- fence. CloudCannon now falls back to parsing the file content as YAML in this case.
  • Fixed an issue where, in some cases, creating multiple files from the same Schema could result in duplicated or incorrect front matter data. This issue also affected body content in data file Schemas (.json, .yml, .yaml, .toml).
  • Fixed an issue where, in some cases, CloudCannon would incorrectly apply YAML front matter indentation when creating new files from a Schema.
  • Fixed an issue where CloudCannon would incorrectly save unknown Hugo shortcodes when the shortcode name contains a / character.
  • Fixed an issue where, in some cases, filtering many files in the Collection Browser caused an error.
  • Fixed an issue where, in some cases, CloudCannon would fail to load preview screenshots on Cards in the Collection Browser.
  • Fixed an issue where CloudCannon did not display unsaved images in Bookshop components.
  • Updated dependencies to patch security vulnerabilities.
Open in a new tab