12 Replies
π™π™§π™žπ™«π™šπ™š [ π™‡π™–π™«π™–π˜Ώπ™šπ™« ]
it worked yesterday not it doesn't work....???? How can i fix it? The already deployed already works which really confuses me It's not the api key nor database, already changed those I'm using vercel as well Has anyone found any solution? Bump :D
Jakov
Jakovβ€’5mo ago
Are you the maintainer of toolkit.dev? If not, you have to wait for the developer to fix it. You cannot remove that issue. That means that the conversation is too long and you have to create a new one or shorten your message
π™π™§π™žπ™«π™šπ™š [ π™‡π™–π™«π™–π˜Ώπ™šπ™« ]
I have and still same issue As well a new api key I am not sadly
Jakov
Jakovβ€’5mo ago
That means that the conversation is too long and you have to create a new one or shorten your message
π™π™§π™žπ™«π™šπ™š [ π™‡π™–π™«π™–π˜Ώπ™šπ™« ]
I have though??? I tried everything New code, mean redeploy with new repo New api keys Everything was changed
Jakov
Jakovβ€’5mo ago
Are you getting that issue on your first message? How long is your message? How long is your conversation?
Jakov
Jakovβ€’5mo ago
Oh Are you self-hosting it? @unc sigma
Jakov
Jakovβ€’5mo ago
You'll have to debug Can you dm me URL to your deployment so I can take a look at the logs? @unc sigma Issue resolved in the DM. Issue was in Toolkit.dev's code where they accidently added google/ to the model name, and when message was being generated, it added google/ for the provider and it fetched model google/google/... instead.

Did you find this page helpful?