Skip to main content
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

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.
Make scenario showing repeated 503 errors on a Magic Meal Kits module

Repeated 503 errors on an MMK module in Make

​
Fix

These steps use the previous screen (v1). The My server (내 서버) screen on the new dashboard (v2) doesn’t have this button yet, so do this on the previous screen at make.magicmealkits.com/app-status. The guide link in the When something goes wrong (문제가 생겼을 때) section of My server also brings you here. We’ll update this page once the new screen has the button.
1

Open the App Status page

Go to make.magicmealkits.com/app-status.
Magic Meal Kits App Status page
2

Open your Magic Meal Kits server

Find the Magic Meal Kits server entry and click it.
Selecting the Magic Meal Kits server on App Status
3

Click Activate

Click Activate to force the server connection to re-activate. This clears the 503 errors.
Activate button to force re-activation
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 for cold-start behavior, or upgrade the memory tier if the errors coincide with heavy load.

​
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. For a faster diagnosis, attach your system logs.