<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflow Automation on App Coding</title>
    <link>https://appcoding.com/tags/workflow-automation/</link>
    <description>Recent content in Workflow Automation on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/workflow-automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An Embedded Workflow Engine With Five Primitives: Trigger, Condition, Action, Wait and Retry</title>
      <link>https://appcoding.com/an-embedded-workflow-engine-with-five-primitives-trigger-condition-action-wait-and-retry/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/an-embedded-workflow-engine-with-five-primitives-trigger-condition-action-wait-and-retry/</guid>
      <description>&lt;p&gt;A user signs up on Monday. If they haven&amp;rsquo;t activated by Wednesday, you send a nudge email, and if the email provider times out, you try a few more times before flagging the account. That&amp;rsquo;s the whole spec. Most teams build it as a cron job that scans for users in the wrong state, a nullable &lt;code&gt;nudge_sent_at&lt;/code&gt; column and a retry loop written late on a Friday. It holds until the cron overlaps itself, or a deploy lands mid-loop, or the provider times out after actually sending the message and one customer gets three emails.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
