> ## 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.

# FAQ

> Answers to the most common Magic Meal Kits questions — finding modules, Notion connection/permission errors, timeouts and duplicate runs, and where to manage connections.

The most common questions from the community, with the fix for each. For server-level
operations (503 errors, slow server, logs, stopping the service) see
the [Troubleshooting](/troubleshooting) guides.

<AccordionGroup>
  <Accordion title="I can't find the Notion Plus modules in Make">
    Two things to check:

    * **Notion Plus is a Pro feature.** It requires a **Pro** license — make sure your
      deployment uses a Pro license.
    * **Add the Notion Plus app and set up its connection.** The modules appear in Make once
      the Notion Plus custom app is added and connected. Manage connections at
      [make.magicmealkits.com/connections](https://make.magicmealkits.com/connections).

    <Note>
      **Bulk Notion (벌크노션) is a separate product.** It automates Notion template updates
      directly and does **not** require a Magic Meal Kits install or a Make connection — so its
      features won't appear as Make modules.
    </Note>
  </Accordion>

  <Accordion title="Notion calls fail with 401 / a permission error">
    The most common cause is that your Notion integration **hasn't been granted access to the
    page or database** you're automating. Issuing the token is not enough — you must add the
    integration to the page/DB itself.

    Full step-by-step fix: [Fix Notion connection & permission errors](/operations/notion-connection).
  </Accordion>

  <Accordion title="Notion writes time out, or my scenario runs twice">
    Two separate effects to know about:

    * **Timeouts.** When a Notion write fails, the Magic Meal Kits server **retries
      internally**. Those retries can exceed the Make module's time limit and surface as a
      timeout. Set an explicit request **timeout** and keep payloads within limits.
    * **Duplicate runs.** Make's **"allow storing of incomplete executions"** option re-runs
      failed scenarios, which can look like duplicate writes. Review that setting if you see
      repeats.

    More detail: [Make integration tips & gotchas](/operations/make-integration-tips).
  </Accordion>

  <Accordion title="A connection suddenly throws a cookie or auth error">
    Cookie/session formats change over time. If a connection starts failing with a cookie or
    auth error, **re-register (reconnect) the connection** — this clears it in most cases. For
    Notion specifically, re-setting the Make Notion connection (log out of Notion, then log
    back in while reconnecting) resolves it. Manage connections at
    [make.magicmealkits.com/connections](https://make.magicmealkits.com/connections).
  </Accordion>

  <Accordion title="Where do I manage my connections?">
    Connection setup and management is centralized at
    [make.magicmealkits.com/connections](https://make.magicmealkits.com/connections). Your
    deployment's API URL and key are shown there (and on the App Status page) — you don't
    configure them by hand. See [Authentication](/authentication).
  </Accordion>

  <Accordion title="My server is down, slow, or I need logs">
    These are covered by the Troubleshooting guides:

    <CardGroup cols={2}>
      <Card title="Persistent 503 errors" icon="triangle-exclamation" href="/operations/fix-503-force-sync" />

      <Card title="Slow / out of memory" icon="gauge-high" href="/operations/upgrade-performance" />

      <Card title="Share system logs" icon="file-arrow-down" href="/operations/share-system-logs" />

      <Card title="Stop or reinstall" icon="power-off" href="/operations/stop-reinstall" />
    </CardGroup>
  </Accordion>
</AccordionGroup>