Failures That Reach a Human

به چه درد می‌خورد

جریانی که بی‌صدا شکست می‌خورد از نبودنش بدتر است، چون دیگر کسی آن کار را دستی انجام نمی‌دهد. این اسکیل مسیر خطا را پیش از مسیر موفق می‌سازد: کار اصلی داخل یک اسکوپ، اسکوپ دوم برای خطا با همه حالت‌ها نه فقط شکست، متن واقعی خطا همراه لینک اجرا و شناسه رکورد، و پایان با وضعیت قرمز. مسیر خطایی که یک بار هم شلیک نشده تزیین است.

خود اسکیل کپی

A flow that fails silently is worse than no flow, because people have stopped
doing the task by hand. Build the failure path before the happy path.

Structure:
- Put the real work inside a Scope named Try.
- Add a second Scope named Catch after it.
- In the Catch scope's run-after settings, tick failed, timed out AND skipped -
  not just failed. A skipped scope is one that never ran, and that is a failure
  too.
- Inside Catch: capture the error detail, write it somewhere durable, notify a
  person or a channel, then terminate the flow as Failed. A caught error that
  ends the run as Succeeded is a lie in your reporting and in anyone's dashboard.

What the notification must contain:
- Flow name, environment, and a link to the run. Without the link the recipient
  cannot act on it.
- The identifier of the record being processed. "The flow failed" is not
  actionable; "order 44812 failed" is.
- The actual error text, not your summary of it.

Ownership, before you ship:
- Do not leave it owned solely by your account and your personal connections.
  When you change roles or a password rotates, the flow dies with it. Add a
  co-owner or run it as a service account.
- Send failure notices to a shared destination, not to one inbox.

Then prove it works:
- Break one step on purpose - a bad id, a missing file - and run it. Confirm
  the notification actually arrived and the run shows as failed.
- An error path you have never fired is not error handling. It is decoration.

The failure this prevents: six weeks of quiet failures, discovered when a
customer asks why nothing was ever sent.

نصبش چطور است کپی

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

برای تو جواب داد؟

از کجا آمده