Skip to main content

Tools Checklists

"

Tools and templates

This page is the utility index for reusable workflow reliability checklists. It points readers to the evidence they should preserve before changing production automation.

Incident evidence checklist

  • Incident start and detection time.
  • Workflow and execution IDs.
  • Original input or event identifier.
  • Last expected step and first unexpected step.
  • Downstream records or side effects already created.
  • Exact error text or HTTP status.
  • Recent workflow, credential, API or schema changes.

Duplicate-action checklist

  • Was there one execution or several?
  • Did the source send the same event twice?
  • Did a timeout or retry occur?
  • Is there a stable event or business key?
  • Does the destination enforce uniqueness?
  • Can replay repeat a completed side effect?

AI action safety checklist

  • Does the model need this tool at all?
  • Is the tool read-only, draft-only or write-capable?
  • Are parameters validated outside the model?
  • Can external untrusted content influence the decision?
  • Is the action reversible?
  • Does high-impact execution require human approval?

Fix verification checklist

Tools and templates

This page is the utility index for reusable workflow reliability checklists. It points readers to the evidence they should preserve before changing production automation.

Incident evidence checklist

  • Incident start and detection time.
  • Workflow and execution IDs.
  • Original input or event identifier.
  • Last expected step and first unexpected step.
  • Downstream records or side effects already created.
  • Exact error text or HTTP status.
  • Recent workflow, credential, API or schema changes.

Duplicate-action checklist

  • Was there one execution or several?
  • Did the source send the same event twice?
  • Did a timeout or retry occur?
  • Is there a stable event or business key?
  • Does the destination enforce uniqueness?
  • Can replay repeat a completed side effect?

AI action safety checklist

  • Does the model need this tool at all?
  • Is the tool read-only, draft-only or write-capable?
  • Are parameters validated outside the model?
  • Can external untrusted content influence the decision?
  • Is the action reversible?
  • Does high-impact execution require human approval?

Fix verification checklist

  • Replay the original failing case.
  • Run one normal neighboring case.
  • Run one relevant edge case.
  • Check downstream business effects, not only workflow status.
  • Confirm monitoring can detect recurrence.
  • Record the final evidence with the incident.

How this page should evolve

As the site accumulates original reliability cases, this page should become the entry point for downloadable regression templates, incident worksheets, workflow review checklists and structured diagnostic trees.

Useful next pages

  • Replay the original failing case.
  • Run one normal neighboring case.
  • Run one relevant edge case.
  • Check downstream business effects, not only workflow status.
  • Confirm monitoring can detect recurrence.
  • Record the final evidence with the incident.

How this page should evolve

As the site accumulates original reliability cases, this page should become the entry point for downloadable regression templates, incident worksheets, workflow review checklists and structured diagnostic trees.

Useful next pages

"

Comments

Post a Comment

Popular posts from this blog

Self-Hosted n8n Keeps Crashing: What Evidence to Collect

" Operations and recovery A self-hosted workflow platform adds infrastructure failure modes to workflow failure modes. Changing container settings, database state and workflow logic at the same time makes diagnosis harder. Resolution rule Change one boundary at a time. Preserve the failing evidence, apply the smallest safe correction, then replay the known case and check the business effect as well as the technical run status. Contents What the symptom actually proves Evidence to collect before changing the workflow Likely failure paths Resolution sequence Prevention design Verify the fix Decision table Sources and scope What the symptom actually proves A self-hosted workflow platform adds infrastructure failure modes to workflow failure modes. Changing container settings, database state and workflow logic at the same time makes diagnosis harder. A useful diagnosis begins by separating what is directly observed from what is only suspected. Execution status, HTTP co...
Post a Comment
Read more

Contact Feedback

" Contact and feedback Useful technical feedback includes enough evidence to locate a problem while protecting credentials, customer data and confidential workflow information. Contents What to include in technical feedback What not to send How to use available site feedback channels What to include in technical feedback The URL of the page you are commenting on. The specific statement, step or link that appears wrong or outdated. The current platform and version where relevant. A link to current primary documentation if you have one. A sanitized example that does not contain credentials or personal data. What not to send API keys, passwords, access tokens or cookies. Customer names, email addresses, financial data or confidential records. Production database exports. Private webhook URLs or credential-bearing screenshots. How to use available site feedback channels Use the feedback or contact channel made available on this Blogger site when enabled. If article comme...
Post a Comment
Read more