[BUG] v0.chats.create 500 internal_server_error

[PaulSinghDev]

All of a sudden the SDK has stopped working. When I request a completion with the chat I am getting:

{"success":false,"error":{"type":"internal_server_error","message":"An unexpected error occurred"}}

An example of the code which is causing this:

const response = await v0.chats.create({
      message: "Make a landing page",
    });

Is there a known outage?

EDIT:

I have added a comment explaining that I think this is more of a poor error message than anything else. I swapped out my key for one of the company's pro account keys and it started working again. This leads me to believe that this is an issue with my account's credits or the token usage estimation going over what is left in my allowance?

Either way I think we need to assess the error message which is sent back to the dev so that we can handle it gracefully.

[JorgeRosbel]

Using exactly the same code, it works correctly for me...

[PaulSinghDev]

Hey @JorgeRosbel sorry I forgot to update this. The issue is the error message. The error was coming as a result of something to do with my API key. I say this as I swapped it out for the company key with a pro account and then the code started working again.

When I go to the v0 dashboard it shows that I still have credits I also noticed that the dashboard says used: never for the API keys which is incorrect as I have used them (hence my usage being at $3.86). Is it likely that the reason for the error is that the prompt may have used more tokens than what my allowance can accomodate?

[JorgeRosbel]

@PaulSinghDev I suppose it is possible to exceed the context window if that is what you mean, but in theory it should throw an error indicating that information and not a 500 error that really tells you nothing

[PaulSinghDev]

Yeah exactly, that was why I initially was leaning towards it being an outage as I just could not get it up and working again until I added the key -- by which time I was just happy to have it working and moved on with life 😄

So, something tells me this is just a poor error message from a catch-all code block to stop the overall app from messing the bed.

[ctate]

Yes, that's correct. 5xx errors are considered a defect. We are actively monitoring these and addressing them as they are reported.

We implemented improvements yesterday that increased our success rate from 92.19% to 99.47%. We hope this leads to a significantly better experience. Please don't hesitate to reach out if you continue to encounter any issues. Thank you!

[PaulSinghDev]

Hey @ctate thanks for taking the time to get back to me! That’s great about the success rates will this be in the latest version on npm? If so I’ll pull it down.

I was noticing a similar issue when using the attachments field but I’ll try again with the new version and report back if it is still there

Thanks again 💪