Skip to main content
These notes apply to every Magic Meal Kits deployment (all apps — Threads, Plaud, Notion, …), since the server runs in your own Google Cloud project. Start here when something’s wrong — pick the symptom that matches.

​
Server stopped or erroring

Free trial ended / activate billing

Your Google Cloud free trial ended and the server stopped — upgrade (activate billing).

Modules keep returning 503

Make scenarios repeatedly fail with 503 — force-reactivate the server.

Notion 401 / permission error

Notion modules fail with 401 or a permission error — grant access and re-set the connection.

​
Tuning & maintenance

Server is slow / out of memory

Slow under heavy load — upgrade the memory tier from Free to Basic.

Building Make scenarios

Find the modules, set timeouts, and avoid duplicate runs in Make.com.

Support asked for logs

Download your system logs from Google Cloud and send them to support.

Stop or reinstall

Stop the service, or reinstall it (with the billing prerequisite).

​
Keeping your deployment running

The Magic Meal Kits server runs in your own Google Cloud project and stays within Google Cloud’s free usage tier for normal use — but the free trial is time-limited.
If you started on the Google Cloud free trial, your server is stopped once the trial ends unless you activate billing (upgrade) first. See Activate Google Cloud billing (upgrade) for the step-by-step guide and what it costs.

​
Stopping or reinstalling the service

You can stop and reinstall the Magic Meal Kits service at any time:
  1. Sign in to Google Cloud at make.magicmealkits.com/google-connection.
  2. Open make.magicmealkits.com/app-status.
  3. Click Stop Service and type magic-meal-kits to confirm.
Full step-by-step guide: Stop or reinstall the service.
Reinstalling requires a healthy Google Cloud billing account. If your Google Cloud billing has an issue, the installation will fail — you must resolve the billing problem first, then reinstall. If you can’t verify the billing status, the cleanest path is to fully delete and reinstall after fixing billing.
After fixing billing or reinstalling, give it 20–30 minutes — don’t redeploy repeatedly. When a server has been down for a while and you reinstall or correct your billing info, the service often does not respond right away: you may see 503 (cold start) or 429 (Rate exceeded) for a time. This is normal warm-up / propagation and usually clears on its own within 20–30 minutes. Please just wait — repeatedly redeploying does not speed it up and can make recovery take longer.