Skip to content

feat: handle extraction failures gracefully and add workspace ID to Slack table - #71

Draft
adamrtalbot wants to merge 2 commits into
mainfrom
feat/handle-extraction-failures
Draft

feat: handle extraction failures gracefully and add workspace ID to Slack table#71
adamrtalbot wants to merge 2 commits into
mainfrom
feat/handle-extraction-failures

Conversation

@adamrtalbot

Copy link
Copy Markdown
Contributor

Summary

  • Catch errors during tw runs dump and tar extraction so one workflow failure doesn't abort the entire run. Failed extractions are reported as FAILED_TO_EXTRACT in the Slack results table.
  • Add Workspace ID column to the Slack results table (sourced from workflow-info.workspaceId).
  • Catches specific exceptions: ResourceCreationError, ResourceExistsError, JSONDecodeError, TarError, OSError.

Test plan

  • Trigger a workflow run and verify the Workspace ID column appears in the Slack table
  • Verify that if one workflow dump fails, the remaining workflows still complete and report
  • Confirm failed extractions show with 💥 FAILED_TO_EXTRACT status in the table

🤖 Generated with Claude Code

…lack table

Catch errors during `tw runs dump` and tar extraction so one failure
doesn't abort the entire workflow. Failed extractions are reported as
FAILED_TO_EXTRACT in the Slack table. Also adds a Workspace ID column.

Generated by Claude Code
The seqerakit exception classes vary across versions (CommandError vs
ResourceCreationError), so catch broad Exception to handle all cases.

Generated by Claude Code
@adamrtalbot

Copy link
Copy Markdown
Contributor Author

Not keen on this because it skips important errors.

@adamrtalbot
adamrtalbot marked this pull request as draft May 13, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant