even using basic documentation as payload ( {“key”: “value”} ) still do errors. lol someone need to fix this
This doesn’t look like an Inventor issue, but rather an issue with the external service you are attempting to contact. Inventor doesn’t print errors in the response body, if an Inventor error occurs while processing the request all output variables will be blank and an error will be emitted.
Can you try re-creating the POST request using a local tool like Insomnia or Postman? Are you sure you are sending data in the correct/expected format of the service you are trying to contact?
Keep in mind that we generally aren’t able to help with external requests. If you’re able to reliably reproduce this issue (where the error only appears with Inventor and maybe against other domains/services), and can show that is is an isolated issue to Inventor, please provide those details.
already done it and success, actually I try to execute groq api and success using postman. I realize it after my current bot not working , and that bot already running for several days before.
Are you making exactly the same request? Are you sure that the request body and other details are the same?
The string “invalid_request_error” does not exist within the Inventor codebase, the error you are seeing is definitely not being generated by Inventor.
I see, appreciate that hint. And I already replicate it,
this is response if we success passing payload
and this is if I dont pass any payload
, and it seems the error comes from third-party, but somehow inventor inject error because that Go error interface showed up too.
Can I debug the block the “Send Request Network Block” ? so I can help to find out the issue
It’s working previous several days, but somehow this morning it’s broken ( with no changes )
We changed network providers earlier today, so its possible that is causing an issue with Groq.
so this is expected or gonna investigate further ?
It’s not expected, but unless others are encountering the same issue, there probably isn’t much we can do about it. I’m checking some basic things to make sure this isn’t an obvious issue on our end, or something specific about Groq’s API.
1 Like
okay appreciate it
I just made a few changes that might help things. Let me know if you notice any improvement.
1 Like
well it seems you find and catch the culprit. It’s all well now , I’m execute manually component and it’s working again. thank you
Great! It looks like there was an issue with the format of body data that was causing issues with how Groq’s API parses data.