> ## Documentation Index
> Fetch the complete documentation index at: https://docs.magicmealkits.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix persistent 503 errors (force re-activate)

> Use this when Make.com scenarios keep failing with 503 from Magic Meal Kits modules — force-reactivate the server from the App Status page.

When your Magic Meal Kits modules in Make repeatedly return **503**, the link between Make
and your server has dropped. Forcing the server to re-activate from **App Status** restores
it.

## When you need this

<Warning>
  **Symptom:** A Make scenario keeps failing on a Magic Meal Kits module with a **503**
  error, and retrying doesn't help — the errors repeat. This means your server is
  temporarily unreachable.
</Warning>

<Frame caption="Repeated 503 errors on an MMK module in Make">
  <img src="https://mintcdn.com/mmk-5fd4bbfe/KDPw8YFM0S5oyWgw/assets/operations/force-sync/symptom.png?fit=max&auto=format&n=KDPw8YFM0S5oyWgw&q=85&s=019f8066fdcf218d7b800b3eef777246" alt="Make scenario showing repeated 503 errors on a Magic Meal Kits module" width="854" height="396" data-path="assets/operations/force-sync/symptom.png" />
</Frame>

## Fix

<Steps>
  <Step title="Open the App Status page">
    Go to [make.magicmealkits.com/app-status](https://make.magicmealkits.com/app-status).

    <Frame>
      <img src="https://mintcdn.com/mmk-5fd4bbfe/KDPw8YFM0S5oyWgw/assets/operations/force-sync/step01.png?fit=max&auto=format&n=KDPw8YFM0S5oyWgw&q=85&s=01d24e230b514159267d7760e505770c" alt="Magic Meal Kits App Status page" width="3202" height="1696" data-path="assets/operations/force-sync/step01.png" />
    </Frame>
  </Step>

  <Step title="Open your Magic Meal Kits server">
    Find the **Magic Meal Kits server** entry and click it.

    <Frame>
      <img src="https://mintcdn.com/mmk-5fd4bbfe/KDPw8YFM0S5oyWgw/assets/operations/force-sync/step02.png?fit=max&auto=format&n=KDPw8YFM0S5oyWgw&q=85&s=5d2c71559606eea102f6fd72c0eac0f3" alt="Selecting the Magic Meal Kits server on App Status" width="1642" height="1036" data-path="assets/operations/force-sync/step02.png" />
    </Frame>
  </Step>

  <Step title="Click Activate">
    Click **Activate** to force the server connection to re-activate. This clears the 503
    errors.

    <Frame>
      <img src="https://mintcdn.com/mmk-5fd4bbfe/KDPw8YFM0S5oyWgw/assets/operations/force-sync/step03.png?fit=max&auto=format&n=KDPw8YFM0S5oyWgw&q=85&s=77c1978e6179a91016f09e306bcea59b" alt="Activate button to force re-activation" width="1742" height="1082" data-path="assets/operations/force-sync/step03.png" />
    </Frame>
  </Step>
</Steps>

<Note>
  After re-activating, give it a moment and re-run your scenario. If 503s persist for more
  than a few minutes, the server may still be warming up — see
  [Troubleshooting](/troubleshooting) for cold-start behavior, or
  [upgrade the memory tier](/operations/upgrade-performance) if the errors coincide with
  heavy load.
</Note>

## Still stuck?

If the errors continue after re-activating, contact support and include your account email
and a short description of the symptom: [Contact 푸르공 on KakaoTalk](https://open.kakao.com/me/pureugong).
For a faster diagnosis, attach your [system logs](/operations/share-system-logs).