Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v3 AI Config issue #14958

Closed
andyburgessmd opened this issue Nov 4, 2024 · 4 comments
Closed

v3 AI Config issue #14958

andyburgessmd opened this issue Nov 4, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@andyburgessmd
Copy link

Checklist

  • I have searched budibase discussions and github issues to check if my issue already exists

Hosting

  • Self
    • Method: docker compose
    • Budibase Version: 3.0.2
    • App Version: 3.0.2

Describe the bug
Using a update form shows AI settings realted errors but nothing is using any AI. The errors was showing an error something like 'Error: No AI Config' so I went to settings where the /builder/portal/settings/ai was shown as default and I added a provider to see if that would fix it. Then I got the message 'Error: No config selected as default AI config',
image

I have tried to go back to settings to set the AI provider as default but it won't allow that and shows this message.
image

I've only found this on the first form I have tried after updating an app to 3.0.2 so nothing else has changed and I'm not going to continue with any others yet in case they break

@andyburgessmd andyburgessmd added the bug Something isn't working label Nov 4, 2024
Copy link

linear bot commented Nov 4, 2024

@shogunpurple
Copy link
Member

Hi @andyburgessmd - looking into this, this feature should be feature flagged and not required if there's no AI config. Must be something to do with paid tiers. Will keep you updated. Best to roll back for now if you are on the premium plan

@andyburgessmd
Copy link
Author

@shogunpurple rolled the app back but still shows this error

@andyburgessmd
Copy link
Author

@shogunpurple 3.0.3 has fixed it. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants