Duaer

Integrations

Common issues with OpenAI in Duaer

Common OpenAI node errors in Duaer: insufficient quota, rate limits, bad requests, and unexecuted referenced nodes.

Insufficient quota detected

The OpenAI account has no credit or is over a usage limit. The Duaer OpenAI shows this on insufficient_quota. In the OpenAI console:

  1. Pick the organization and project that own the API key in the upper-left selectors.
  2. Check that the organization Billing page shows credit. A fresh top-up can take a while to apply.
  3. Check organization Limits and project Limits for a usage cap you have reached.

Back in Duaer, confirm the OpenAI credential holds a key from the funded account and that the node uses that credential. If the error persists after a top-up, create a new key and try again.

OpenAI: Rate limit reached

OpenAI returned 429 because of too many requests in a short time.

Turn on Retry On Fail in the node Settings with a longer Wait Between Tries (ms). For many items, batch them with Loop Over Items and add a Wait between batches.

Bad request - please check your parameters

OpenAI rejected the request and Duaer could not read the reason. Check the model name and parameters first. Then send the same request from HTTP Request with the same credential to see the raw OpenAI error.

Node '…' hasn't been executed

An expression references a node that did not run this time. Run up to that node first, or change the expression. For a node on a branch that may not run, check $("Node name").isExecuted first.

Questions

What fixes Insufficient quota detected on the Duaer OpenAI node?

In the OpenAI console, confirm the organization and project have credit and are under their limits, then confirm the Duaer OpenAI credential uses a key from that account.

In this section