Agent Publishing Bug - Old Variables Persisting

Support
1

I’m experiencing a critical issue with Agent publishing where old variable names persist in production even after updating the system prompt with new variable names.

Issue Summary:

I have a MindStudio agent (Pinch Response 2) that receives 7 input variables from Make.com: normalized_question, answer_text, answer_source, confidence, couple_name_1, couple_name_2, and tone.

However, the published agent is checking for different variable names that no longer exist: guest_message, answer_content, answer_source, confidence_score, etc.

Steps I’ve Taken:

  1. Updated the System Prompt to reference the correct variable names ({{normalized_question}}, {{answer_text}}, etc.)

  2. Clicked Publish and waited 1-2 minutes

  3. Tested via API — error persists

  4. Cleared browser cache and tried incognito mode

  5. Created a brand new Agent (Pinch Response 2) from scratch with the correct variable names

  6. Updated System Prompt in the new agent with identical variable names

  7. Simplified the Automations prompt to minimal text

  8. Clicked Publish again and waited

Current Behavior:

  • The draft shows correct variable names in the editor

  • The published agent still returns errors looking for old variable names

  • The error message references variables I explicitly removed from the system prompt

  • MindStudio throws “Internal Error” screens intermittently (Error ID: c64678c9af4f4503a00efd04bdd7cad3)

Attached Evidence:

  • Image 1: Internal Error on published agent

  • Image 2: Debug report showing Agent receives all correct inputs but still fails

  • Image 3: System Prompt editor showing correct variable names defined

  • Image 4: Runtime variables showing Agent 2 receives: answer_source: “wedding_table”, answer_text: “Cocktail attire”, normalized_question: “What is the dress code?”, confidence: 0.95, couple_name_1/2, tone: “fun”

Question:

Is there a cache/sync issue with Agent publishing? I’m at a loss for what to do. I’ve tried every solution possible.

I’m trying to launch this product and this is blocking MVP. Any urgent guidance appreciated.

Error ID for reference: c64678c9af4f4503a00efd04bdd7cad3

Thanks!

image.pngimage.pngimage.pngimage.png

2

Mindstudio1
Mindstudio11372×872 102 KB

Mindstudio2
Mindstudio21400×858 165 KB

Mindstudio3
Mindstudio31456×831 160 KB

mindstudio 4
mindstudio 4915×1316 143 KB

3

Hi @hacks,

Thank you for your post, and for the detailed breakdown!

Looking at what you’ve shared, the screenshots cover everything, with only one piece missing: the Start block. In MindStudio, any variables coming in from an external source, like Make.com, need to be introduced as Launch Variables in the Start block before the agent can recognize them. If the Start block still references the old variable names, the published agent will keep looking for those regardless of what’s in the System Prompt.

Could you share a screenshot of your Start block? That’ll help me understand if that may be causing the issue.

This guide also walks through how to trigger a MindStudio agent from a Make scenario, including how Launch Variables are set up:

4

Thank you!

You were right, it was a Launch Variable issue. I didn’t have it setup.

I am still having issues restoring previous versions of the agent seamlessly. I noticed that when I click ‘restore’, the old system prompt doesn’t load unless I refresh the page.

Just wanted to point that out. It caused some of my confusion, thinking it was a system prompt issue or that the system prompt wasn’t being published correctly.

5

Hi @hacks,

Glad to hear the agent’s working now!

Apologies for the system prompt issue on restore. I’ve flagged it for our engineers to investigate and will follow up once I have an update. This looks like a UI bug and shouldn’t affect the agent’s actual performance, so refreshing after restoring a previous version should work in the meantime.