Nylah
Nylah4d ago

API error re-try

Hello guys, can please help me? I've added an API call node with on fail (retry) option. In my called API I purposely return a 400 error. When I have check the API run logs it only has the initial run and don't have run logs for the retry. Am I doing something wrong?
2 Replies
AI Support
AI Support4d ago
AI Support Bot Information
<@439401662197530635> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human! Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers. Please note: Team members will review and answer the questions on best efforts basis.
AI Support
AI Support4d ago
AI Response
It seems that the issue of not seeing the retry logs for your API call node when a 400 error is returned is not specifically addressed in the available FAQs. However, there are a few possibilities and things you might consider checking: 1. Node Configuration: Double-check the configuration of your API call node and ensure that the retry option is set up correctly. 2. BuildShip Logs: Verify if there are any settings or permissions related to logging levels that might prevent retry attempts from being logged. 3. Node-Specific Behaviors: Some nodes may not log retry attempts by default if they are deemed non-critical or if logging is too verbose. 4. Support Request: If none of the above seems to be the cause, this might be an unintended behavior or a bug that needs addressing. You would want to raise a support request via the BuildShip in-app support for further assistance. In case none of these are helpful, it might be beneficial to contact BuildShip support directly for more specific guidance regarding the retry logging of API call nodes.
BuildShip AI Support