Incorrect Production Agent Used
Hi
Issue
I duplicated a project I made for an ecommerce store (Store A) for another ecomm store (Store B).
While building the agent for Store B, everything was working fine. When I embedded the agent onto Store B's shopify store, it had the styling and initial messaging of Store B, but used Store A's variables and knowledge base.
I.e. Visually looked like Store B, but used Store A's conversation logic & features.
I used the correct API keys and production/project ID.
What I want
For my production for Store B to use my actual project...
I probably have to just re-build the project from scratch and change all the variables which will take a few hours.
Was wondering if there is any faster way.
4 Replies
Hey there!
What you’re seeing usually happens when the production version of the new project was never republished after you finished your edits:
1. When you duplicate Store A ➞ Store B, Voiceflow automatically gives the copy its own project ID, but it also keeps the last published version from the original project (i.e. the Store A-style KB, variables, flows).
2. All embeds / DM API calls that use the alias
3. Visual tweaks to the chat widget (colours, greeting, etc.) live outside the project’s conversation logic, so they showed up right away – but the underlying dialog and KB are still the “old” production build. Quick fix (no rebuilding needed) • Open the Store B project • Confirm everything looks good in the canvas & Knowledge Base
• Press the green Publish button (top-right) → add optional release notes → confirm
• Wait a few seconds, then refresh the chat widget on your Shopify site The widget will now pull the freshly-published Store B logic/KB with the same API key and project ID you’re already using. Tip: while you’re iterating you can test the development environment (Prototype tool or DM API with
2. All embeds / DM API calls that use the alias
version=production will keep serving that last published version until you click Publish again.3. Visual tweaks to the chat widget (colours, greeting, etc.) live outside the project’s conversation logic, so they showed up right away – but the underlying dialog and KB are still the “old” production build. Quick fix (no rebuilding needed) • Open the Store B project • Confirm everything looks good in the canvas & Knowledge Base
• Press the green Publish button (top-right) → add optional release notes → confirm
• Wait a few seconds, then refresh the chat widget on your Shopify site The widget will now pull the freshly-published Store B logic/KB with the same API key and project ID you’re already using. Tip: while you’re iterating you can test the development environment (Prototype tool or DM API with
version=development) before pushing changes live.
Docs for reference: https://docs.voiceflow.com/docs/publishing-agents-to-production
That should save you from rebuilding anything – just republish and you’re good to go! 🎉Forgot to mention, I have already published it several times.
That didn't help
I have embedded this agent on my agent testing website though and it works perfectly fine.
However, on Shopify it is acting weird.
Both Store A & Store B are Shopify ecom stores by the way
Duplicating finished project for another client is scary because it can remember stuff, e.g I had e-com setup with knowledge base etc and when I duplicated it, it remembered stuff from the other project even though the knowledge base was empty visually
Yeah I have that exact same thing only in production though. Do you recommend just downloading the template & then importing the project instead of duplicating?