Variant revisions

Variant Revision UUID

When you deploy or redeploy a variant to any environment (e.g., Production or Staging), Formsort creates a unique 36-character variant_revision_uuid. This UUID represents the exact state of the variant at the time of deployment and can be found in the History tab of the variant.

Pinning

When a responder loads a flow and begins interacting with it, a variant_revision_uuid will be loaded based on the responder_uuid cached in their browser. This “pins” the responder to that exact variant revision on return visits, ensuring a consistent experience in terms of content, style, and logic.

This pinning behavior helps maintain:

• A seamless experience for returning users

• Cleaner cohort analysis, since responders in-flight on older revisions won’t be affected by new deployments

To bring responders onto the latest revision, see Superseding existing versions.

Preventing pinning

There are two main ways to bypass variant pinning:

• Enable Start each session as a new responder in your variant settings

• Use your browser’s incognito mode, which doesn’t store responder_uuid during incognito sessions

💡 Pro tip: Testing a recent change but still seeing an old version? Open the form in an incognito window to make sure you're seeing the latest deployed revision!

Checking Variant Caching

If you’re troubleshooting and want to confirm which variant revision is cached:

1. Open your live flow.

2. Right-click anywhere and select Inspect to open your browser's developer tools.

1. Go to the Network tab.

2. Look for a fetch request with the name of the variant deployment ID.

3. In that request, you’ll find the variant_revision_uuid.

You may need to reload the page after opening the Network tab—the fetch call is made once when the flow initially loads.

---

Force‑Loading a Specific Revision

If you need to test or share an exact revision, append the variantRevisionUuid parameter to your form’s URL:

https://your-form-url?variantRevisionUuid=YOUR_UUID_HERE

Replace YOUR_UUID_HERE with the target revision’s variant_revision_uuid.

💡 Use this sparingly—hardcoding a revision UUID bypasses the normal publish workflow and can prevent future live updates from taking effect.