A real test message for one channel
Send test on a notification channel sends a real delivery to that channel alone, and the result is listed in Delivery history.
More in Notifications.
Changelog
Everything you can see or use that changed, newest first.
Page 5 of 8, 75 changes
Send test on a notification channel sends a real delivery to that channel alone, and the result is listed in Delivery history.
More in Notifications.
Storage shows each volume's size separately, so one volume Cloud cannot read no longer hides the others. Its tables are paged, backup schedules are cards named after their service with icon controls, and a volume's row opens its service.
More in Volumes.
Each card on Domains shows the page served on the domain once HTTPS is active, its status chip, and every control on one line.
More in Domains.
Creating a database, an application from the catalogue, or attaching a volume now asks for Automatic backup: Daily, Weekly, Monthly or No automatic backup. Backups go to the platform's own backup storage, with no destination to set up.
More in Backups.
Each form that creates a service ends in an Order summary: the size, its CPU and memory, its hourly rate and a monthly estimate, and whether automatic backups are included.
More in Sizes and replicas.
Cloud emails your account's address when your balance runs low, when a grace period starts, when the account is suspended and when it is active again. Notifications lists these as Automatic account emails, apart from the channels you add.
More in Notifications.
Add a service has a Services group. One press on Create service makes the whole application: its image, its port, its volume and its generated credentials. A service whose setup could not finish says so on its Overview, with Try again.
More in The application catalogue.
Deployments has a Filter: All statuses, In progress, Successful, Failed or Cancelled.
More in Deployments.
The Dashboard shows your counts and one service's CPU, memory, network and block I/O, and the analytics screen now opens it. Storage also lists the volumes a database or a compose stack manages for itself, marked "Managed by service".
More in A tour of the console.
When a service's container keeps exiting, its Overview says "The engine keeps restarting this service", with how many times it has started and stopped and the engine's last lines about it.
More in Service lifecycle.