Foto Master

Cloud Disconnects Mid-Event

Updated 5 days ago · 5 min read

A mid-event cloud disconnect is one of the worst feelings in this business -- the booth is mid-session, guests are queued up, and suddenly AI features stop working or photos stop sharing. The good news: FMX is designed to keep operating in offline mode, and your photos queue locally and re-sync when the connection returns. This article explains exactly what happens during a disconnect, how to verify connectivity, and how to set yourself up so a Wi-Fi blip never ruins an event.

Quick Diagnostics

When the cloud disconnects mid-event:

  1. Don't panic and don't restart FMX. A restart can lose queued photos and pending AI jobs.
  2. Check your Wi-Fi signal first -- the venue's Wi-Fi is the typical cause.
  3. In FMX, open FMX Main Dashboard > Cloud status indicator to confirm the disconnect and see whether photos are queueing locally.
  4. Switch to your mobile hotspot if Wi-Fi can't be recovered quickly. FMX will reconnect automatically.

Tip: A peripheral coming loose mid-event (for example, a Circle Ring whose USB-C or power cable jiggles out) can look identical to a cloud disconnect from the operator's side. When a disconnect happens, check both the network and the physical cabling on accessories before assuming the cloud itself dropped.

Common Issues

Cloud connection drops and AI features stop working

Problem: Mid-event, the AI Draw Me, AI background removal, or AI style filters stop responding. Customers see a "processing" spinner that never completes.

Cause: AI features run in the Foto Master Cloud and require a live internet connection. When the connection drops, AI jobs pause. Photo capture, basic effects, and printing continue working in offline mode.

Solution:

  1. Verify you have internet -- open any browser tab on the mini-PC and load google.com.
  2. Check the Wi-Fi signal strength in the Windows taskbar. If you're at one bar or in the "limited connectivity" state, move closer to the router or switch networks.
  3. If you have an AI step in your workflow that's stuck, the workflow has a built-in 120-second timeout (Draw2Life and similar steps). After the timeout, the workflow advances and the photo prints without the AI effect.
  4. For the rest of the event, you can either wait for connectivity to return or temporarily skip the AI step in the workflow.

Cloud disconnects but the booth keeps working

Problem: You see a "cloud disconnected" notification but the booth is still capturing photos.

Cause: This is the expected behavior. FMX continues to operate offline for core photo booth functions. Photos queue locally and sync when the connection returns.

Solution:

  1. Continue running the event normally. Photos are saved locally on the mini-PC.
  2. Sharing features (SMS, email) will queue -- the booth tries again as soon as it reconnects.
  3. Cloud Event Gallery uploads will queue in the same way.
  4. Once connectivity returns, FMX automatically processes the queue. You don't need to do anything manually.

How to verify your connection mid-event

Problem: You're not sure if the issue is connection or something else.

Solution:

  1. In FMX, go to FMX Main Dashboard > Cloud status indicator. A green indicator means connected and authenticated. A yellow or red indicator means there's a problem.
  2. Check the Windows network icon in the taskbar. A globe icon with no Wi-Fi waves means you're disconnected. An exclamation mark means you have Wi-Fi but no internet.
  3. Open cmd and run ping 8.8.8.8 -- this tests internet without DNS dependencies. If you get replies, the network is working but Foto Master Cloud may be slow.
  4. Check Foto Master Cloud status at cloud.fotomaster.com -- if the cloud service itself is down, no setting on your booth can fix it; wait it out.

Common causes of mid-event Wi-Fi drops

Cause 1: Venue Wi-Fi quotas / time-outs. Many venues issue 1-hour or 4-hour Wi-Fi sessions that auto-disconnect. Reconnect through the captive portal in the browser.

Cause 2: VPN interference. If the mini-PC has a VPN client (NordVPN, ExpressVPN, etc.) installed and it auto-connects on Wi-Fi, it will block FMX's cloud calls. Disable any VPN before events.

Cause 3: Router overload. At weddings or crowded events, dozens of phones compete for the venue's Wi-Fi and degrade performance for everyone. A mobile hotspot on a separate carrier solves this.

Cause 4: Foto Master Cloud service issue. Rare, but it happens. Check cloud.fotomaster.com and our status page.

Recovery: photos auto-sync when connection returns

Problem: Connection was down for 30 minutes. What happens to all the photos taken during the outage?

Cause: FMX queues every photo, every share request (SMS / email), and every cloud upload locally on the mini-PC.

Solution:

  1. Once connectivity returns, FMX automatically uploads queued photos to the Cloud Event Gallery and processes pending shares.
  2. You can verify the sync by going to FMX > Queue Management (see Queue Management Overview) -- you'll see the queue draining.
  3. If a share fails permanently (e.g., the customer's phone number was wrong), it'll be marked as failed in the queue. You can manually retry or skip.
  4. Do not close FMX until the queue is empty -- if you close mid-sync, FMX will resume on next launch but it slows things down.

Best practices to prevent mid-event disconnects

  • Use a dedicated mobile hotspot as your primary connection at events. Venue Wi-Fi is unreliable.
  • Always carry a backup hotspot on a different carrier (e.g., AT&T primary + Verizon backup).
  • Test your hotspot at the venue 30 minutes before doors open -- some venues have spotty cell signal.
  • Disable Windows automatic updates during events -- a forced reboot mid-event is worse than any cloud issue.
  • Disable VPN clients on the booth's mini-PC.
  • Position the booth near a known-good signal location -- not in a basement, not behind metal walls.

Tip: Sluggish mirror behavior during events is often a symptom of poor connectivity (FMX retrying cloud calls) rather than a hardware issue. Switching to a hotspot often fixes it instantly.

Related Articles

Was this helpful?

Related articles