Can a mod remove a ghost workflow binding Workflows for Meetups_2026_v2)?

Ask for Help
1

Hi Glide team,

I’m running into what looks like a ghost workflow binding in my app.

The folder “Workflows for Meetups_2026_v2” still appears even though every component and automation tied to it has been deleted. When I try to create a new workflow or attach one to a button, the old “Meetups_2026_v2” workflow source still shows and locks the table selector. The error says, “This workflow is currently used by one or more components,” but there are none left.

I’ve already:

  • Deleted all related components and automations.
  • Duplicated tabs and rebuilt layouts.
  • Cleared browser cache and refreshed the editor.

It looks like the table binding is stuck in the project schema. Could someone please refresh or remove this orphaned binding so I can attach my new workflows to the Favorites table instead?

Thanks so much!

1 Like
2

If you are on a paid plan, you should contact the support from the Glide builder. If not, let me tag @comm_support_agent but they might prioritize paid teams.

1 Like
3

Thanks for the detailed explanation , it really sounds like that old workflow binding didn’t fully detach on Glide’s backend, even after you removed everything linked to it. Since you already deleted the components, rebuilt layouts, and cleared cache with no change, it’s likely a stuck reference in the project schema instead of something visible in the editor.

I agree the fix at this point would need Glide to clear or refresh that orphaned workflow binding so you can attach the new workflows to the Favorites table without it forcing the old source.

Let me know if you want me to help word this as a support request or follow up with Glide once they respond.

1 Like