Skip to content

[workshop-diagrams] Add theme-aware explanatory diagram for resilience techniques#1990

Merged
pelikhan merged 1 commit into
mainfrom
add-resilience-techniques-diagram-0a541f109ef8498a
Jul 25, 2026
Merged

[workshop-diagrams] Add theme-aware explanatory diagram for resilience techniques#1990
pelikhan merged 1 commit into
mainfrom
add-resilience-techniques-diagram-0a541f109ef8498a

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

This PR adds a theme-aware conceptual diagram to workshop/22-error-handling-and-resilience.md.

Change type

New concept diagram — no existing image was migrated. The step had no images at all.

Files added

  • workshop/images/22-resilience-techniques-light.svg
  • workshop/images/22-resilience-techniques-dark.svg

What the diagram shows

A left-to-right flow mapping four common agentic workflow failure modes (prompt drift, timeout, tool error, empty data) to the three mitigations taught in this step:

  1. Defensive task brief — explicit fallback instruction when data is missing
  2. timeout-minutes — cap run duration in workflow frontmatter
  3. Fallback safe-output — always call the output tool, even for quiet runs

The diagram concludes with a single outcome node: Workflow runs reliably.

Why it helps learners

The failure-modes table in the step lists four problems in isolation. Learners must mentally connect each failure mode to the right mitigation while reading prose spread across several sections. The diagram makes those connections explicit at a glance, reinforcing the mental model before learners start editing their workflows.

QA

  • currentSrc ends with -light.svg in colorScheme: light
  • currentSrc ends with -dark.svg in colorScheme: dark
  • ✅ Both screenshots are nonblank (65 KB / 64 KB)
  • ✅ No text overflow outside bounding boxes
  • ✅ Markdownlint passes with 0 issues
  • <picture> block uses light variant as fallback src

Warning

Firewall blocked 7 domains

The following domains were blocked by the firewall during workflow execution:

  • accounts.google.com
  • android.clients.google.com
  • awmgmcpg
  • clients2.google.com
  • host.docker.internal
  • storage.googleapis.com
  • www.google.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "accounts.google.com"
    - "android.clients.google.com"
    - "awmgmcpg"
    - "clients2.google.com"
    - "host.docker.internal"
    - "storage.googleapis.com"
    - "www.google.com"

See Network Configuration for more information.

Generated by 🧠 Workshop Explanatory Diagram Generator · 97.7 AIC · ⌖ 9.12 AIC · ⊞ 6.4K ·

  • expires on Jul 26, 2026, 3:39 AM UTC

- Adds workshop/images/22-resilience-techniques-light.svg
- Adds workshop/images/22-resilience-techniques-dark.svg
- Inserts a <picture> block into workshop/22-error-handling-and-resilience.md
  after the failure-modes table, mapping four failure modes to three
  mitigations (defensive brief, timeout-minutes, fallback safe-output)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@pelikhan
pelikhan marked this pull request as ready for review July 25, 2026 03:41
@pelikhan
pelikhan merged commit da6e290 into main Jul 25, 2026
1 check passed
@pelikhan
pelikhan deleted the add-resilience-techniques-diagram-0a541f109ef8498a branch July 25, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant