When the Network Disconnects or the Page Closes

If preparing the runtime environment takes more than about 15 seconds, the page asks you to wait a little longer. Projects that have not been used recently may need more time; a startup request waits up to 90 seconds. If startup ultimately fails, follow the on-screen prompt to retry.

A brief network interruption or closed page does not delete saved Projects, Chats, or build progress. Reopen the same Chat, and Eazo restores whether the task is running, waiting for confirmation, paused, or complete.

After recovery:

If it still shows working, continue waiting;
If a confirmation card appears, complete it;
If Continue Build appears, click it;
If a retry is required, retry the current step rather than creating the same Project again;
If history is restored but no safe continuation point exists, send one new message explaining the next step.

In V5 Chat, the editor remains available while the runtime starts, chat history is restored, a previous message is confirmed, or the connection recovers. Send is temporarily disabled, and the composer shows what it is waiting for. If the chat connection is lost, a reconnecting notice also appears above the editor. Once the Chat is ready, send the message manually; it is not sent automatically. Unsent content is not restored after refreshing or closing the page. Sending waits for receipt confirmation, and you can keep editing while you wait. If delivery is not confirmed, a warning appears and your input stays in place. Check the Chat before resending to avoid duplicates.

Messages load with up to 3 automatic attempts, each lasting at most 30 seconds. Any successful attempt displays the messages. If all 3 attempts fail, loading stops and Recover workspace becomes available. Recovery only starts when you click the button. It may interrupt the current task; saved files are kept. Messages reload after recovery. Check the Chat and task status before restarting unfinished work.

Eazo does not treat an ordinary temporary reconnect as an App failure. Rerun work only when the page explicitly reports failure and provides a retry action.

Continue in Eazo Mobile

Mobile and web should show the same saved Chat state. Keep waiting while work runs, complete a design, requirements, or configuration card when a decision is needed, and click Continue Build for a paused build.

After a temporary disconnection or backgrounding the mobile App, reopen the original Chat and check the latest state before starting another build.