molecule-ai/docs
35
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(blog): debug failed workspaces without leaving Canvas

Browse Source 
Content for internal#8 / PR #1178 launch coverage.
Angle: EC2 console output surfaced directly in Canvas — no more
tab-switching to AWS Console.

~180 words.
This commit is contained in:
molecule-ai[bot] 2026-04-21 03:38:29 +00:00 committed by GitHub
parent a6d9902816
commit e00012be3d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
content/blog/2026-04-21-failed-workspace-ec2-console/index.mdx Normal file
View File

@ -0,0 +1,20 @@
---
title: "Debug Failed Workspaces Without Leaving Canvas"
description: "Molecule AI Canvas now surfaces EC2 console output directly in the failed workspace view — no more tabbing to the AWS Console to understand what went wrong."
publishedAt: 2026-04-21
tags: [canvas, devops, observability, ec2, workspaces]
---
When a Molecule AI workspace fails, the reason lives in the AWS EC2 console. Until today, that meant opening the AWS Console, finding the right instance, pulling the console log, and figuring out what happened — while your workspace sat failed and your team waited.
That's now unnecessary.
Canvas now surfaces `last_sample_error` and the full EC2 console output directly in the failed workspace view. You open the error panel, read the output, identify the root cause, and fix it — all without leaving Molecule AI.
The trigger is a workspace that transitions to `failed` state. Molecule AI captures the EC2 console log from that point and attaches it to the workspace record. It appears in the error panel as soon as the failure is detected, ready to read.
The impact is simple: one tool, one context. Debug in Canvas, fix, redeploy.
If you're self-hosting Molecule AI, update to the latest release and the feature is active immediately. For hosted deployments, it's live now.
Next time a workspace fails, open the error panel before you open AWS. You'll find what you need there.