Data Sync Issues
Resolve problems with real-time updates, stale data, and synchronization across devices.
Firebuzz uses real-time synchronization to keep your data current across all devices and team members. Here's how to troubleshoot sync issues.
How Firebuzz Keeps Your Data in Sync
Firebuzz automatically keeps your data current across all devices and team members. Changes appear instantly without needing to refresh your browser manually. This works through a persistent connection between your browser and Firebuzz's servers, which is why a stable internet connection is important for the best experience.
Common Issues
Changes Not Appearing in Real-Time
Edits made by you or team members are not showing up immediately.
Solution:
-
Check your connection:
- Automatic updates require a stable internet connection
- Look for connection indicators in the app
-
Hard refresh the page:
- Press
Ctrl+Shift+R(Windows) orCmd+Shift+R(Mac) - This forces a fresh data fetch
- Press
-
Check for connection blocking:
- Some corporate firewalls block live update connections
- Contact your IT team to whitelist Firebuzz domains
-
Disable VPN temporarily:
- Some VPNs interfere with automatic updates
Real-time sync requires WebSocket connections. If updates are consistently delayed, your firewall may be blocking these connections.
Seeing Outdated Data
Information appears stale or out of date after refreshing.
Solution:
-
Clear browser cache:
- Old cached data may be displayed
- Press
Ctrl+Shift+Delete, then clear cache and cookies
-
Check your workspace:
- Ensure you are viewing the correct workspace
- Data is workspace-specific
-
Verify project context:
- Switch projects and back to force a data refresh
- Click the project switcher in the sidebar
-
Sign out and back in:
- Refreshes all session data
- Go to your avatar in the bottom left and select Log out
Conflicting Edits
Multiple people editing the same item causes conflicts.
Solution:
Firebuzz handles conflicts automatically:
- Last write wins — The most recent save is preserved
- Check version history — View and restore previous versions if needed
- Coordinate edits — Communicate with team members when editing shared items
For landing pages, version history allows you to view and restore previous versions. Access it from the landing page editor header by clicking the History button.
Analytics Data Not Updating
Analytics seem stuck or not showing recent activity.
Solution:
- Check the time period to ensure you are viewing the correct date range
- Select correct environment by toggling between Preview and Production data
- Wait for processing, as analytics may have a few minutes delay
- Click Refresh on the analytics page
Analytics data may have a processing delay of 2-5 minutes. This is normal and ensures accurate aggregation of events.
Campaign Status Not Updating
Campaign status shows as one thing but should be another.
Solution:
- Refresh the page, as status changes may need a manual refresh
- Check all landing pages to ensure all pages are ready for publish
- Verify domain configuration, as domain issues can block status changes
- Check the flow to ensure there are no validation errors preventing publishing
Best Practices for Sync
- Use a stable internet connection
- Refresh periodically during long sessions
- Coordinate with team members on shared edits
- Use version history to recover lost changes