You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running this same script with a previously function API key results in { "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT" } }
I have records of proper results from my code using the API before ~9:02 AM today. My next attempt at using this same API occurred at 1:54PM and returned this error. In attempting to figure out what happened, I resorted to trying this sample script which I'd based my processing on. It is now returning this same error.
Actual vs expected behavior:
A proper response from the test query.
Any other information you'd like to share?
This API key is still functional; other (text-only, no upload) prompt give appropriate results.
The text was updated successfully, but these errors were encountered:
jxyzn
changed the title
generative-ai-python/samples/rest /files.sh no longer functions starting between 9AM and 2PM Pacific on 2024-11-11
generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT starting between 9AM and 2PM Pacific on 2024-11-11
Nov 11, 2024
jxyzn
changed the title
generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT starting between 9AM and 2PM Pacific on 2024-11-11
generative-ai-python/samples/rest /files.sh fails with INVALID_ARGUMENT response starting between 9AM and 2PM Pacific on 2024-11-11
Nov 11, 2024
Description of the bug:
Running this same script with a previously function API key results in
{ "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT" } }
I have records of proper results from my code using the API before ~9:02 AM today. My next attempt at using this same API occurred at 1:54PM and returned this error. In attempting to figure out what happened, I resorted to trying this sample script which I'd based my processing on. It is now returning this same error.
Actual vs expected behavior:
A proper response from the test query.
Any other information you'd like to share?
This API key is still functional; other (text-only, no upload) prompt give appropriate results.
The text was updated successfully, but these errors were encountered: