Studio-Web Continuity and Sync

Studio-Web Continuity and Sync

When Studio and the web platform are connected through your account, your Pipes, snippets, projects, and other assets can stay in sync across devices. This chapter explains how sync works in practice — what it does, how to set it up, common workflows, and what to do when things get out of alignment.

How Sync Works

Sync keeps your Studio data and your web account in step. When you create or update a Pipe, snippet, or project in Studio, those changes can be pushed to your cloud profile. When you save a Pipe from the web catalog, it appears in your synced Library.

The key concept: sync is continuity tooling, not a replacement for local backups. Your local data is always the primary copy. Cloud sync adds an additional layer of accessibility and cross-device availability on top of that.

Studio supports two sync modes:

You can switch between modes anytime in Settings.

First-Time Setup

Setting up sync for the first time:

1. Link your account — Complete the account linking flow in Connecting Your Account.
2. Verify entitlement status — Sync features require an appropriate plan. Confirm your plan status on My Plans.
3. Check sync status — In Studio Settings, look for the sync status indicator. It should show a healthy baseline after linking.
4. Run a small test — Make a minor change (rename a snippet, update a Pipe description) and verify it appears on the web side in My Desk or Library.
5. Confirm both directions — Save a Pipe from the web catalog and verify it appears in your Studio library.

Note: During first sync, Studio and the web reconcile their data. Don't delete local assets until you've confirmed the cloud profile has what you expect. The reconciliation is designed to be safe, but verifying is always smarter than assuming.

Common Workflows

Discover on web, run in Studio

1. Browse the Pipes catalog and find a workflow you want to try.
2. Save it to your desk.
3. Open Studio — the Pipe should appear in your synced library.
4. Import it into your active Pipes and run a test generation.

Create in Studio, publish to web

1. Build and validate a Pipe locally in Studio (see Pipes & Workflows).
2. Once it's stable and synced, go to My Desk on the web.
3. Find the synced Pipe and use the publish flow from there (see Web Pipes Discovery and Publishing).
4. Verify the published detail page has correct metadata and dependencies.

Multi-device continuity

1. Link both devices to the same web account.
2. Enable cloud sync on both.
3. Changes made on one device sync to the cloud profile and become available on the other.
4. If both devices make changes to the same item, a conflict may be flagged — resolve it from My Desk.

Troubleshooting Sync

When sync isn't behaving as expected, work through these checks in order:

1. Verify account identity — Make sure the same account is linked on both Studio and web. Mismatched accounts won't sync.
2. Check session freshness — If your session has expired, sync won't run. Refresh in Studio Settings.
3. Check sync status — The sync indicator in Studio shows whether sync is running, paused, or erroring. Look at the specific status message.
4. Check entity visibility — Open My Desk and verify your expected items are there. If they're missing, sync may not have completed its latest cycle.
5. Try a small test change — Edit something minor and watch whether it propagates. This narrows down whether the issue is broad or specific to one item.

If sync is in a confused state:

• Check device registration and heartbeat health in Devices.
• Look for dedupe or repair actions in the sync settings.
• Don't bulk-delete local data as a "reset" — that can make things worse if the cloud doesn't have a complete copy.

Tip: Most sync issues resolve by refreshing the session, waiting for the next sync cycle, and checking again. If the issue persists after a full cycle, check device health and sync mode settings.

Local-Only Mode

If you don't want cloud sync at all — either temporarily or permanently — switch to local only mode in Studio Settings. In this mode:

• No data is sent to or read from the cloud.
• Your Studio installation works independently.
• Account linking stays active (for entitlements and future re-enablement) but sync transport is paused.

You can switch back to cloud-enabled mode anytime. When you do, Studio will reconcile local and cloud state before resuming regular sync.

Next: Quick Reference