{
  "id": 14855086,
  "title": "Connected steps are not a workflow",
  "url": "https://urgent.news/2026/10/16/connected-steps-are-not-a-workflow",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-16T03:13:53.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/usehive/connected-steps-are-not-a-workflow-58jd"
  },
  "original_language": "en",
  "account": "A customer requests a refund, and the request exists within the support desk while the order resides in the billing system. The agent, upon reading both, determines that the refund is not warranted according to the rules, proceeds to issue the refund, and informs the customer. These rules are not defined within any API, so refunds under fifty dollars proceed smoothly, but anything above that threshold requires a manager's approval. Testimonials are held for human approval before being released. Escalations occur after two interactions with the customer. However, these interconnected steps are not a true workflow. The agent reads the order in the billing system, then transfers this information to the support desk, where it becomes a snapshot of a moment that has already occurred. The billing system allows for refunds under one permission set, while the support desk adds a customer note under a different set. Crucially, there is no confirmation that the refund has actually been processed before the note is sent out. This showcases that connected steps alone do not constitute a workflow. The agent carries out every action permitted by the apps, yet the outcome is incorrect because the rules and handoffs exist in the gaps between the systems.",
  "summary": "Take a task that crosses two apps. A customer asks for a refund. The request lives in the support desk. The order lives in the billing system. End to end, the agent reads both, decides against the refund rules, issues the refund, and confirms back to the customer. The rules are in neither API. Refunds under fifty dollars are fine when the order is paid and never refunded before. Over that, a…",
  "key_points": [
    "Refund request exists in support desk, order in billing system",
    "Refunds over $50 require manager approval, not defined in API",
    "No confirmation of refund processing before customer note sent"
  ],
  "editors_take": "Fragmented data handoffs between disconnected systems create operational gaps that allow human error to bypass established rules and compromise the accuracy of final customer outcomes.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}