Dashboard

Partner outages

What the file partner and AI partner notices mean, what can fail while one shows, and how each clears on its own.

On this page

Modulify builds on a few outside services, which it calls its partners. Two of them take part in nearly everything you do while you build:

  • The file partner stores your site's code. What chat changes is saved there, and the preview, publishing and code backups all read from it.
  • The AI partner runs the AI that builds your site in chat.

When one of them has trouble, Modulify itself is still up, but a step that goes through that partner can be slow or fail. So that a failure never arrives without a reason, Modulify shows a short notice where you are working, says what may fail, and takes it away again once the partner is back. You never have to close a notice or report it.

The file partner

Where it shows What it reads What it is about
Above the prompt box on the dashboard, and on the Create tab of the app Our file partner is having issues, creating a site may fail. Creating a site
Above the chat box, in the editor and in the app Our file partner is having issues, saving may fail. Saving changes
In the status pill above the preview, in the editor and in the app Could not load your files, our file partner is having issues Loading your files

Modulify reads two signals. One is the partner's own public status report. The other is Modulify's own requests to the partner, from every site and not only yours: when many of them fail in a short time, the notice shows even before the partner reports anything. An open tab asks for the latest state every so often while it is in front, and as soon as you come back to it. The app checks the same way while it is open, so a notice can appear or go away while you watch.

The notice does not disable anything. You can still create a site and send messages, and only the step that needs the partner can fail. It clears on its own once the partner's report is clear again and Modulify's own requests to it have stopped failing.

Creating a site

Every new site starts with its own copy of the starting code at the file partner, made before the AI starts building. When that copy cannot be made, no site is created: a Site creation failed toast says why and nothing is built. Your prompt stays in the box, so you can send it again once the notice is gone.

Saving changes

After each chat turn, the preview saves what changed to the file partner, and a publish saves first as well. While the partner has trouble a save can fail, and the pill above the preview can read Could not save your changes. for a few seconds. The changes stay in the preview, and the next save that goes through takes everything that was not saved yet, such as the one after your next chat turn.

Loading your files

When the preview starts, it loads your files from the file partner. If that fails while the partner has trouble, the pill reads Could not load your files, our file partner is having issues with Try again next to it. Use the preview covers what the preview retries on its own first.

Publishing

A publish reads your site's code from the file partner. When it cannot, it stops before building and nothing is published, so the version already live keeps serving. See When a publish fails.

The AI partner

Above the chat box, in the editor and in the app, the notice is titled Temporary issues and reads Things may be slow or fail due to a third-party outage, should resolve shortly.

It does not show just because the partner reports trouble. It shows once a run in your tab has failed while the partner reports an outage, so it explains a failure you have already seen instead of warning about one that may never reach you. A run stopped by something that has nothing to do with the partner, such as running out of credits or another run already going, does not bring it up.

Modulify reads the partner's own public status report. The editor checks it when the chat opens, every 30 seconds while the tab is in front, as soon as you come back to the tab, and right after a run fails. The app checks the same way while it is open.

The notice goes away once the partner reports that it is back. It also goes away as soon as you send a message, answer a question or press Continue, and when a run finishes. It comes back only if a run fails again while the outage lasts.

Once it is gone, Try again on the failed reply runs the same request again, and files a failed run already wrote stay written, see When a run fails. A failed reply that reads The AI service is temporarily overloaded. Please try again shortly! with the code SC-2002 comes from the AI partner too: it was too busy to take the request, and Try again sends it again.

Only one notice sits above the chat box at a time. A notice that editing is paused or blocked for your site's code comes first, then the file partner notice, then this one. So while the file partner has trouble as well, a failed run shows the file partner notice and not Temporary issues.

Your live site

Neither notice is about the site your visitors see. A publish that cannot reach your code stops before anything changes, so the version already live keeps serving. AI that your site calls from its own code is separate from the AI partner: modulify/fast and modulify/smart move to another provider on their own when one is down, see Pick a model.

If a notice stays

A notice clears on its own once the partner is back, so you never need to report one. If a notice stays up for a long time, or something keeps failing with no notice at all, message the team from the support chat.

Next