Skip to main content
GET
List Cloud Function Runs

Automatic retries when the Nexor API is busy

If a function calls the Nexor API during a traffic peak, the API can answer 429 (rate limited). When that happens, Nexor runs the function again automatically a few minutes later, so it doesn’t miss the event. A run is retried only when all of these are true:
  • At least one request to the Nexor API got a 429.
  • Every request the function made was a read (GET, HEAD, or OPTIONS).
  • The function produced no effects.
Nexor retries up to 5 times. Each attempt waits at least one minute, and the waits are spread out so many functions don’t retry at the same moment. Every attempt appears in run history as its own run, so a blocked run followed by a successful one is expected.
A function that sends a write or changes a lead is never retried, because running it twice could repeat that change. A 429 from another service is not retried either.

Authorizations

X-API-Key
string
header
required

API key for authentication. Keys are prefixed with nxr_live_.

Query Parameters

page
integer
default:0
Required range: x >= 0
limit
integer
default:50
Required range: 1 <= x <= 100
function_id
string<uuid>

Filter by function.

lead_id
string
triggered_only
boolean
default:false
status
enum<string>
Available options:
success,
error,
timeout

Response

Successful response.

runs
object[]
required
total
integer
required
page
integer
required
limit
integer
required
success
any
required

Observed top-level response field.

Last modified on October 20, 2026