Skip to main content
Your copy of OpenEmail changes only when you agree to it. Your agent does the work; you say yes before each deploy, and you hold the Render account it runs in.

Updating your copy

OpenEmail never installs an update by itself, and it doesn’t check for one. Update on a regular rhythm anyway: your copy pins a Shopify API version, and a copy left unchanged long enough can lose Shopify sync when Shopify retires that version. Ask your agent: “Update OpenEmail to the newest version. Tell me what changes before you deploy.”
1

Your agent records where you are

  • It reads get_status and notes the running version (running_commit), the install state and any holds.
  • It records the last successful deploy of both Render services, so there is a known version to go back to.
Checkpoint: your agent has told you the running version and the version it can go back to.
2

Your agent explains the update; you agree

  • It picks the newest version, unless you name another, and reads the change log for everything since your running version.
  • The change log names any work beyond a deploy: new settings, new Shopify permissions or webhooks, data backfills, a Shopify API version move.
  • It tells you what the update brings and what it needs from you, then waits for your yes.
Checkpoint: you’ve said yes to one named version, knowing what it needs from you.
3

Your agent deploys both services

  • The same version goes to the web service first, then the worker.
  • Each service runs its database migrations before it starts. If a migration fails, the old code keeps serving.
  • Your agent confirms each deploy in Render, then checks that get_status shows the new version.
Checkpoint: Settings > Activity shows an Update deployed row with the new version and the migrations it applied.
4

Your agent refreshes your app folder

  • The folder on your computer that holds your agent’s OpenEmail instructions is brought to the same version.
  • If the update changes what your AI client may run without asking, your agent shows you the difference first. Your AI client then asks you to confirm.
Checkpoint: your agent reports the app folder on the new version.
5

You grant new Shopify permissions, if any

  • When the update adds Shopify permissions or webhooks, your agent releases the new app configuration.
  • Open OpenEmail in your Shopify admin and approve the new permissions.
Checkpoint: your agent reports the new version running on both services, and no new hold in get_status.
Going back moves code, not data. Your agent can rebuild an earlier version on both services, with your yes. Database contents and migrations stay as they are, so it checks the change log for compatibility first. Render’s own Rollback button, on each service’s Deploys page, is a separate route you take yourself.

Your backup

  • Render’s point-in-time recovery is the only backup. There is no off-site copy.
  • Seven days back. On the Professional workspace plan setup uses, a paid Render database can return to any moment in the last seven days. A Hobby workspace keeps three.
  • A restore makes a new database at the moment you choose. The original stays as it was.
  • Your data stays yours. You own the Render, database and sender accounts, and can export the database and move your copy.

Restoring a backup

A restore takes your copy offline while it switches databases, and holds all sending until it has caught up. Ask your agent to guide you through it: most steps happen in your Render dashboard.
1

Agree on the restore point

  • Choose the moment to go back to and accept the downtime.
  • Your agent records the running version and the database being replaced. The version stays the same through the whole restore.
Checkpoint: you and your agent have agreed on one restore point and the downtime.
2

Stop both services

  • In Render, stop the worker first and wait for it to shut down, then stop the web service.
  • Nothing may run against either database while you switch.
Checkpoint: neither service is running in Render.
3

Restore the database

  • Open the database’s Recovery page in Render, choose Restore Database, and pick the agreed point.
  • Write down the exact time of that point, with its time zone, and wait until the new database is available.
Checkpoint: the new database is available, and you’ve noted the restore point with its time zone.
4

Point both services at it

  • On each service’s Environment page, set two values together and choose Save only, which doesn’t deploy:
    • DATABASE_URL: the new database’s connection URL.
    • RESTORED_FROM: the restore point in UTC, such as 2026-10-30T12:34:56.000Z.
  • Save the pair on both web and worker before starting either. Leave every encryption and link key unchanged.
  • Keep the database URL inside Render. Never paste it into chat.
Checkpoint: both services have the new DATABASE_URL and RESTORED_FROM saved, and neither has started.
5

Start web, then the worker

  • Start the web service first. Your agent checks that get_status lists restore under holds.
  • Only then start the worker. Recovery begins.
Checkpoint: get_status shows the restore hold and an unfinished restore matching your restore point.
6

Let recovery finish

  • OpenEmail reads back PostShiba’s delivery reports and resyncs Shopify from the restore point. A failed step retries by itself, and the hold stays until both finish.
  • When both are done, the restore hold lifts on its own. Don’t clear it by hand or remove RESTORED_FROM before then.
  • Your agent then checks the other holds: a finished restore doesn’t mean every other check passes.
Checkpoint: get_status shows no restore hold and no unfinished restore.

What a restore can’t bring back

  • Some unsubscribes. One-click unsubscribes after the restore point, from contacts who aren’t Shopify customers, are lost. Shopify can’t supply them again.
  • Instance-only history. Recovery rebuilds what Shopify and PostShiba hold, not everything. If Render’s backup is lost too, hand-subscribe statements and consent history held only in OpenEmail can be lost for good.
Keep the daily rhythm in the daily check.
Last modified on November 5, 2026