AI Chats and Vectors no longer loading on pages with public link

,

Hi there, we are currently testing chat bot features and vectors that could be accessed via a public page for our external customers. It worked fine until this morning.

When in ‘edit’ or ‘private’ mode (as in people logged in on retool with their login details), all our AI queries and vectors are still loading & running fine.

But as soon as we go to the public page URL of that app, all AI features are no longer working. This is very recent, those features were working absolutely fine up until a few days ago when looking at the public URL.

Let me know what kind of additional details we can provide to help you pinpoint the issue? The instance where we are building this app is https://angsanatools.retool.com/

Thank you

Jerome

Hello @Jeje, thanks for reporting this. Could you share the link to your public app so I can test it out on my end?

@ChiEn Of course, thank you. I will message you a custom link privately if that’s ok as each public URL is customised per customer with a temp password while we’re still building this internally.

Hey @Jeje, I understand now. It looks like the link you shared still requires login, so it would not be considered a public link.

Here is how public links are defined in the Retool docs:

Thank you for coming back to me so quickly. Our login moving forward will be a simple JWT token as we wanted to embed this retool app on our website, where our clients would have a login/pass, and once logged in they would have access to all our tools via that public URL. Our clients won’t have a need to login on Retool.

We are a bit surprised because that page has been working for 6months now for our different tests. Is it because AI queries and vectors are now locked on public pages? Using AI moving forward will require to be logged in on Retool?

Thank you for your help

Hey @Jeje, Great news, we've shipped a fix for AI chats and vectors loading on pages. Could you check again and confirm whether everything is working on your end?

By the way, External Users would be better suited for what you are doing. Authenticating users in a public app isn't supported, and it also falls outside our Terms of Service. Let me know if you have any other questions! :raising_hands:

1 Like

Hi @ChiEn thank you for the heads up, we tested it and that worked.

Yes the auth is temporary for our tests and the plan would be to have it fully public once we’re ready to go live with it.

Thank you again!

1 Like

Glad to hear, sounds good! @Jeje :smiley: