Skip to main content

I would like to report a significant degradation in the performance and accuracy of the AI-generated sequence diagrams.

Until recently, your AI functionality worked flawlessly. I’ve been using very clear, consistent prompts, most of which were generated and refined with ChatGPT, and they used to generate precise, correct diagrams immediately on the first try.

However, something seems to have changed in the past few days. I’ve noticed:

  • The AI interface looks different and responds differently to prompts.

  • Instructions that previously worked are now ignored (e.g., “do not use swimlanes” or “label each step as Step 1, Step 2…”).

  • The AI often duplicates actors, misorders steps, or skips key actions.

  • Diagrams are sometimes correct only after 15–20 retries, which never used to be the case.

It seems that either the AI engine or its prompt parser has been modified recently, because this behavior was never a problem before.

This unreliability is starting to impact my workflow significantly, and I'm now actively considering purchasing a separate diagram AI tool to handle sequence process maps more consistently.

Could you please confirm if any updates were made recently to Lucidchart’s AI engine?
And more importantly: how can we restore previous accuracy and behavior?

Hi ​@Hulio1952, thank you for posting in the Lucid Community. I’m sorry to hear you are encountering problems here! I am raising this internally with the development team.

Can you please send a temporary Support PIN for one of the documents that you’re noticing this in? This will allow me to take a closer look at the issue you’re experiencing. For more information on generating a Support PIN, check out this Help Center article. This PIN can only be accessed by Lucid support staff, so you can share the pin directly within this thread.

 

 


PIN :duV9GjDxJPzBx4207175357

 


All recent process diagrams with status “Draft” are incorrectly generated by the AI 


Any update on the issue?


Hi ​@Hulio1952, Thank you for providing that information and for your patience here as we looked into this. I’ve added your post to a report for our development team, logging this issue. They are actively working on getting performance back up.

While we don’t have an estimated timeline for a fix, we understand this issue is impacting your workflow, and we sincerly apologize for the disruption. 

I will update this thread with any new information. Please follow along on this thread for updates, and post any additional questions or concerns below.


Reply