Skip to main content
Solved

AI error: "Something went wrong on our end"

  • March 10, 2026
  • 12 replies
  • 170 views

Forum|alt.badge.img

Hello team,

when submitting an AI prompt on Lucidchart I only get the error “Something went wrong on our end”. I tested it on different browsers, and in incognito but the error is the same.

By looking at the network requests I can see the call returns a 500 error. See screenshot below.

How to proceed?

Thanks

 

Best answer by Micah

Hi all, I’m glad to share some good news from our development team to start the week: the technical issues affecting Lucid AI have been fully resolved, and all services are now back online and operating normally. We appreciate your patience as we worked with our provider to address this problem.

 

If you continue to experience any issues, please let us know immediately!

Comments

Zuzia S
Forum|alt.badge.img+8
  • Lucid community team
  • March 10, 2026

Hi ​@luisdavid7, thanks for reaching out! I am very sorry for the issue you are experiencing.

Our Development Team is urgently looking into this, and we expect the issue to be resolved shortly. I will make sure to update you as soon as the issue is resolved. In the interim, I apologize for any inconvenience the issue causes.

Feel free to let me know if you have any further questions. Thanks for your help and patience!


Becca G
Forum|alt.badge.img+4
  • Lucid support team
  • March 10, 2026

Hi there ​@luisdavid7!

I have good news! Our development team has let me know that the issue should now be resolved. I’m sorry for any inconvenience this may have caused. If you’re still seeing the issue or have any other questions, feel free to reach out. I’m happy to help!


Forum|alt.badge.img
  • March 12, 2026

Are there any additional updates on this issue? Becca G’s last comment indicates that the issue has been fixed, but I’ve been unable to use LucidAI most of yesterday and today because of this issue. 


Zuzia S
Forum|alt.badge.img+8
  • Lucid community team
  • March 13, 2026

@bgarvey thank you for following up in this thread and I am sorry to hear that the issue persists on your end!

Could you try opening your document in a private or incognito window? Could you also try connecting to a different network or disconnecting from your VPN (if applicable)? Sometimes account performance issues can be related to internet security/speed or browser issues. These steps will help us eliminate that possibility. For help with opening an incognito window, please see this community post.

If those don’t resolve the problem, can you please send a screenshot of the error message you see as well as the associated Javascript Console output after reproducing the issue? You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).

Thanks in for your help and patience!


Forum|alt.badge.img

I have the same issue. Javascript Console log included.

https://community.lucid.co/product-questions-3/ai-error-something-went-wrong-on-our-end-12935?tid=12935&fid=3
Unchecked runtime.lastError: Cannot create item with duplicate id Add other item https://community.lucid.co/product-questions-3/ai-error-something-went-wrong-on-our-end-12935?tid=12935&fid=3
Unchecked runtime.lastError: Cannot create item with duplicate id Save all entered data https://community.lucid.co/product-questions-3/ai-error-something-went-wrong-on-our-end-12935?tid=12935&fid=3
Unchecked runtime.lastError: Cannot create item with duplicate id Generate Secure Password https://community.lucid.co/product-questions-3/ai-error-something-went-wrong-on-our-end-12935?tid=12935&fid=3
6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16  POST https://ai.lucid.app/evo-tool-call 500 (Internal Server Error)
k @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onScheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleMacroTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
we @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
(anonymous) @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
n.<computed> @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
instrumentation @ c34864a7e670e15a847440ce20af5feb93ef325acc31845092ed7752962d2d.js.gz:11
(anonymous) @ 38af15f01eeb79e4fa47a49801171159754f9e56a67c26bde99a62ac8df14d.js.gz:198
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
Fg @ 38af15f01eeb79e4fa47a49801171159754f9e56a67c26bde99a62ac8df14d.js.gz:196
UcKld @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:506
UcJld @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:502
UcLld @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:502
enqueue @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:509
(anonymous) @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:510
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
execute @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:510
Uc6Sd @ 38af15f01eeb79e4fa47a49801171159754f9e56a67c26bde99a62ac8df14d.js.gz:200
(anonymous) @ 38af15f01eeb79e4fa47a49801171159754f9e56a67c26bde99a62ac8df14d.js.gz:202
(anonymous) @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
Uc6cb @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
Ucf @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
UcLo @ 38af15f01eeb79e4fa47a49801171159754f9e56a67c26bde99a62ac8df14d.js.gz:202
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:269
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:816
(anonymous) @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
Uc6cb @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
Ucf @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
UcbDm @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:816
Xvl @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:817
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:219
b @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
invoke @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onInvoke @ c710a051191d16d1f922db0aa31aec8aedae3a28c466a390fe524d4aaf427f.js.gz:272
invoke @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
run @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
(anonymous) @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onInvokeTask @ c710a051191d16d1f922db0aa31aec8aedae3a28c466a390fe524d4aaf427f.js.gz:272
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
runTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
X @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
g.useG.invoke @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
E._.args.<computed> @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
setTimeout
E @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onScheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
scheduleMacroTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
we @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
(anonymous) @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
n.<computed> @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
Ucg_c @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:41
Uce_c @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:40
setTimeout @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:43
setTimeout @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:112
(anonymous) @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:112
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
delay @ 8e8e9fdb54930c0e80cf35ab31e77c05d2888c0129a64ba6880ce990634542.js.gz:112
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:219
(anonymous) @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
Uc6cb @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
Ucf @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
UcZtm @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:219
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:817
(anonymous) @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
x @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
Uc6cb @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
Ucf @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
Gyg @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:817
(anonymous) @ 6ce2e3aaea124f0cd8913b4e53fb09dbc6bbafa0e8beac857069043985f927.js.gz:4283
b @ 2f23d775516f8b57ce4f354250b45bcfa9c63bf303d35e52e3749e17b2bd9f.js.gz:3
invoke @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onInvoke @ c710a051191d16d1f922db0aa31aec8aedae3a28c466a390fe524d4aaf427f.js.gz:272
invoke @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
run @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
(anonymous) @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:17
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
onInvokeTask @ c710a051191d16d1f922db0aa31aec8aedae3a28c466a390fe524d4aaf427f.js.gz:272
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
runTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
X @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
invokeTask @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
O @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
A @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
K @ 6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16
6350cce1c7f451a02ec711f3b1b631ff8aa26a55f859386f4a65821e3a0e12.js.gz:16  POST 


ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
2Grammarly.js:2 grm ERROR [iterable] ░░ Not supported: in app messages from Iterable
write @ Grammarly.js:2
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
Grammarly.js:2 grm ERROR [iterable] ░░ Not supported: in app messages from Iterable
write @ Grammarly.js:2
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/check-product-switch:1  Failed to load resource: the server responded with a status of 500 ()
ai.lucid.app/evo-tool-call:1  Failed to load resource: the server responded with a status of 500 ()
3Grammarly.js:2 grm ERROR [iterable] ░░ Not supported: in app messages from Iterable


Forum|alt.badge.img+1
  • April 14, 2026

hi , I am encountering the same issue  when trying to generate a process diagram with AI. “ Something went wrong at our end” . How do I resolve this ?

 


Ambar D
Forum|alt.badge.img+11
  • Lucid community team
  • April 14, 2026

Hi ​@jhurford89 and ​@Gita, thank you for your reports. I apologize for the issue you’re experiencing. 

At this time, Lucid is currently experiencing an issue with Lucid AI. Our Development Team is looking into this issue, and we expect the issue to be resolved shortly. We’ll provide an update via this thread as soon as the issue is resolved.


Ambar D
Forum|alt.badge.img+11
  • Lucid community team
  • April 14, 2026

For any users who may come across this post, Lucid is currently experiencing an issue with Lucid AI. When accessing Lucid AI, you may encounter an error message that says “Something went wrong on our end”.

Our Development Team is looking into this issue, and we expect the issue to be resolved shortly. We’ll provide an update via this thread as soon as the issue is resolved.

 


Micah
Forum|alt.badge.img+20
  • Lucid community team
  • April 17, 2026

Hi all, passing along an update from our development team:

We are still actively working on a fix to the problems with Lucid AI. This issue originates with our AI provider, and we are working closely with their teams to correct it as quickly as possible. Our teams are taking active steps to resolve this issue and safeguard against future outages to the best of our ability. We will continue to share updates as we have them.


Micah
Forum|alt.badge.img+20
  • Lucid community team
  • Answer
  • April 20, 2026

Hi all, I’m glad to share some good news from our development team to start the week: the technical issues affecting Lucid AI have been fully resolved, and all services are now back online and operating normally. We appreciate your patience as we worked with our provider to address this problem.

 

If you continue to experience any issues, please let us know immediately!


Forum|alt.badge.img+1
  • April 22, 2026

ISSUES HEAVY, SAME PROBLEM


Zuzia S
Forum|alt.badge.img+8
  • Lucid community team
  • April 22, 2026

Hi ​@scarb, I am sorry to hear that issues persist on your side! 

I have followed up in your community post here to support you further and gather information to investigate this again. We appreciate your help and patience!