"My Components" list is empty after transferring site; newly created instances are not saved

Finsweet Components
1

Description

  • When launching the Finsweet Components app in WebFlow, the “My Components” list is always empty, despite the fact that the site includes 5 different slider instances.
  • This issue started occurring after transferring the site to a separate workspace.
  • If I run a scan of inaccessible pages, or use the “cleanup” function, then the plugin does locate the 5 slider instances and I can see them in the “My Components” list again. However, if I close the Finsweet app and reopen it, the list is empty again.
  • Even if I create a new slider instance, and republish the site, the new instance does not appear in the “My Components” list unless I run another scan. Then it disappears again as soon as the FinSweet Components app is closed.

Site URL

I am not able to share the site URL at this time. I may be able to share more information via DM, but since this issue occurs with the app UI itself, not with the generated WebFlow components, I’m not sure whether the site url would be helpful.

Steps to Reproduce

  1. Launch the Finsweet Components app in WebFlow. See that the “My Components” list is empty.
  2. Run a scan to detect existing instances. The app locates them and adds them to the “My Components” list.
  3. Republish the site, as prompted by the app.
  4. Close the Finsweet Components app.
  5. Launch the Finsweet Components app again and see that the “My Components” list is empty again.

Expected Behavior

I expect that the “My Components” list remains populated with the existing slider instances, and does not require a manual scan to find the slider instances every time that the app is launched.

Actual Behavior

Each time that the app is closed, the “My Components” list is cleared out and requires a new scan before they are found again.

Video/Screenshots

When first launching the app, before running a scan to locate instances:

Screenshot 2026-01-23 at 5.06.44 PM
Screenshot 2026-01-23 at 5.06.44 PM1722×1390 149 KB

Additional Context

  • I have attempted the following steps to debug:
    • Uninstalling and reinstalling the Finsweet Components app
    • Deleting the Finsweet Components custom code and republishing the site so that the custom code is regenerated

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

2

Hey @luke3

Looks like you’ve found an interesting edge case with Components after a workspace transfer. When sites move between workspaces, the app sometimes loses track of component instances - they’re still on your site (which is why scanning finds them), but the connection gets broken

Seems the app is falling back to a temporary DOM scan instead of reading its stored project mapping

Have a look at some fixes to try;

Workspace Transfer Breaks Internal Site ID Mapping (Most Likely)

When a Webflow site is moved to another workspace, the internal site/project ID changes, but some apps (including Finsweet Components) cache the previous ID.

Fix (important order):

Open Webflow Designer

Remove Finsweet Components app completely

Publish site (with app removed)

Hard refresh browser
Ctrl + Shift + R

Re-install Finsweet Components app

Publish site again

Why this works:

Forces Finsweet to generate a new site binding token

Clears orphaned references to the old workspace project


App Can’t Save State Due to Permission Scope

After workspace transfer, your account may not be the “owner” of the project.

Check:

  • Project Settings → Permissions
  • Make sure your user role is:
    • Admin or Designer
    • NOT “Editor”

The Components app needs write access to store component registry data.



Partial Publish & so Components Won’t Persist

The app stores component data only when all static pages are published.

Instead of publishing selected pages, publish all pages

Also publish to production domain not only staging



CMS / Draft Page Edge Case

Your screenshot warning is relevant:

Components on draft, protected, CMS pages won’t appear automatically

If your sliders are inside:

  • CMS templates
  • Draft pages
  • Utility pages
  • Password protected pages

Run scan once then:

  1. Open one of the pages with sliders
  2. Make a tiny edit (space key)
  3. Publish all pages

This forces Webflow to rebuild page DOM snapshots that Finsweet indexes


A last check is to make sure you didn’t scan on staging then reopen on prod

Let me know how it goes

Thanks

3

Hi @jesse.muiruri, thanks very much for your response!

After trying out several of the troubleshooting methods that you suggested, I believe I have found the cause of the issue. The initial steps didn’t have any effect, but this section of your reply gave me a clue (the last part in particular):

I forgot to mention in my initial message that I did enable password protection on the site after it was transferred to the other workspace. Based on your message, I figured that this could be related to the issue, so I tried the following:

  • disabled password protection on the site
  • ran another scan with Finsweet Components
  • published the site
  • closed Finsweet Components
  • relaunched Finsweet Components

After taking those steps, the “My components” list was populated as expected. It seems like the password protection setting is what was causing the issues. It’s unfortunate if that is indeed the case, since we need to have the password protection enabled (at least for now), but now that I know what the likely cause is, I can work around it more effectively.

Thanks again for your help, it’s much appreciated!

4

Perfect!

Thanks @luke3 for updating on what worked for you

Seems a bummer that it couldn’t work with the password protected pages but now that the ‘my components’ list was re-populated automatically, subsequent visits might work with the password-protection on

All good though