<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on API Coding</title>
    <link>https://apicoding.com/tags/automation/</link>
    <description>Recent content in Automation on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Make for APIs: Rerun Only the Steps Downstream of an Endpoint That Changed</title>
      <link>https://apicoding.com/make-for-apis-rerun-only-the-steps-downstream-of-an-endpoint-that-changed/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/make-for-apis-rerun-only-the-steps-downstream-of-an-endpoint-that-changed/</guid>
      <description>&lt;p&gt;A nightly job pulls a users endpoint and an orders endpoint, normalizes both, joins them on customer ID and renders a report. On most nights the upstream data hasn&amp;rsquo;t changed since the last run. The job doesn&amp;rsquo;t know that, so it downloads and parses everything, reruns every transform and writes the same report again. If the API bills per call, or one step takes twenty minutes, you pay for the same answer every night.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
