import { Prose } from "@/components/equip/prose";

export default function Example() {
  return (
    <Prose>
      <h1>Moving from cron jobs to scheduled functions</h1>
      <p>
        Cron on a single server was fine while we had one server. With six, the same job ran six times every night,
        and the invoice run sent some customers two emails. This is how we moved every job to scheduled functions in
        two weeks.
      </p>
      <h2>What changed</h2>
      <p>
        Each job is now a function with a schedule next to it in the repository. The platform runs it once, in one
        region, and keeps the last 30 runs with their logs. A failed run retries twice and then pages whoever is on
        call.
      </p>
      <ol>
        <li>List every crontab entry and who owns it.</li>
        <li>
          Port the jobs one at a time, starting with the ones that are <strong>safe to run twice</strong>.
        </li>
        <li>Leave the old entry commented out for a week before deleting it.</li>
      </ol>
      <blockquote>
        <p>The hardest part was not the code. It was finding out what the 2:15 job did.</p>
      </blockquote>
      <h3>What we would do differently</h3>
      <p>
        Write down the expected run time for each job on day one. The first time a job took four times longer than
        usual, nobody noticed for a month. The <a href="#alerts">duration alerts</a> we added afterwards would have
        caught it the same night.
      </p>
    </Prose>
  );
}

<div class="eq-prose"><h1>Moving from cron jobs to scheduled functions</h1><p>Cron on a single server was fine while we had one server. With six, the same job ran six times every night, and the invoice run sent some customers two emails. This is how we moved every job to scheduled functions in two weeks.</p><h2>What changed</h2><p>Each job is now a function with a schedule next to it in the repository. The platform runs it once, in one region, and keeps the last 30 runs with their logs. A failed run retries twice and then pages whoever is on call.</p><ol><li>List every crontab entry and who owns it.</li><li>Port the jobs one at a time, starting with the ones that are <strong>safe to run twice</strong>.</li><li>Leave the old entry commented out for a week before deleting it.</li></ol><blockquote><p>The hardest part was not the code. It was finding out what the 2:15 job did.</p></blockquote><h3>What we would do differently</h3><p>Write down the expected run time for each job on day one. The first time a job took four times longer than usual, nobody noticed for a month. The <a href="#alerts">duration alerts</a> we added afterwards would have caught it the same night.</p></div>

import { Prose } from "@/components/equip/prose";

export default function Example() {
  return (
    <Prose style={{ width: "100%" }}>
      <h2>Rate limits</h2>
      <p>
        Every response carries the <code>X-RateLimit-Remaining</code> header. When it reaches zero, the API answers
        429 and <code>Retry-After</code> says how many seconds to wait.
      </p>
      <pre>
        <code>{`if (res.status === 429) {
  const wait = Number(res.headers.get("Retry-After"));
  await sleep(wait * 1000);
}`}</code>
      </pre>
      <table>
        <thead>
          <tr>
            <th>Plan</th>
            <th>Requests per minute</th>
            <th>Burst</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td>Hobby</td>
            <td>60</td>
            <td>10</td>
          </tr>
          <tr>
            <td>Team</td>
            <td>600</td>
            <td>100</td>
          </tr>
          <tr>
            <td>Enterprise</td>
            <td>6,000</td>
            <td>1,000</td>
          </tr>
        </tbody>
      </table>
      <hr />
      <p>
        Limits apply per API key, not per account. Ask support if a batch job needs a higher burst for a day.
      </p>
    </Prose>
  );
}

<div style="width:100%" class="eq-prose"><h2>Rate limits</h2><p>Every response carries the <code>X-RateLimit-Remaining</code> header. When it reaches zero, the API answers 429 and <code>Retry-After</code> says how many seconds to wait.</p><pre><code>if (res.status === 429) {
  const wait = Number(res.headers.get(&quot;Retry-After&quot;));
  await sleep(wait * 1000);
}</code></pre><table><thead><tr><th>Plan</th><th>Requests per minute</th><th>Burst</th></tr></thead><tbody><tr><td>Hobby</td><td>60</td><td>10</td></tr><tr><td>Team</td><td>600</td><td>100</td></tr><tr><td>Enterprise</td><td>6,000</td><td>1,000</td></tr></tbody></table><hr><p>Limits apply per API key, not per account. Ask support if a batch job needs a higher burst for a day.</p></div>

import { Prose } from "@/components/equip/prose";

export default function Example() {
  return (
    <Prose style={{ maxWidth: "52ch" }}>
      <h3>Changelog, 12 November</h3>
      <ul>
        <li>Branch previews now build in half the time on large monorepos.</li>
        <li>
          Logs can be filtered by request id from the <a href="#logs">log viewer</a>.
        </li>
      </ul>
      <p style={{ color: "var(--eq-ink-3)", fontSize: "var(--eq-text-s)" }}>
        Shipped by the platform team. Questions go to #platform-help.
      </p>
    </Prose>
  );
}

<div style="max-width:52ch" class="eq-prose"><h3>Changelog, 12 November</h3><ul><li>Branch previews now build in half the time on large monorepos.</li><li>Logs can be filtered by request id from the <a href="#logs">log viewer</a>.</li></ul><p style="color:var(--eq-ink-3);font-size:var(--eq-text-s)">Shipped by the platform team. Questions go to #platform-help.</p></div>