// HTTP 409

This component follows a heartbeat

component_bound: This component takes its status from a heartbeat, so its status cannot be set by hand.

What to do

Leave status out, or send "heartbeat_id": null to stop following the heartbeat and then set the status.

Sending the same request again will give the same answer. Change the request first.

Common causes

  • The component was bound to a heartbeat with heartbeat_id.

What the response looks like

{
  "error": {
    "code": "component_bound",
    "message": "This component takes its status from a heartbeat, so its status cannot be set by hand.",
    "fix": "Leave status out, or send \"heartbeat_id\": null to stop following the heartbeat and then set the status.",
    "retryable": false,
    "docs": "https://setget.net/errors/component_bound"
  }
}

message often has more detail than shown here, such as the exact field, line or limit involved. fix says what to do next and retryable says whether trying again unchanged can help.

All error codes

CodeHTTPMeaningWhat to do
unknown_tool 404 No tool has that name Check the spelling, or search the catalogue at https://setget.net/tools or GET /v1/tools/search?q=...
invalid_input 400 The input is not valid Fix the fields listed under "problems" and send the request again. Each tool page lists its inputs with examples.
tool_timeout 422 The tool took too long Try a smaller input, or a simpler pattern or expression.
tool_memory 422 The tool ran out of memory Try a smaller input, or split it into parts and process each part separately.
output_too_large 422 The result is too large to return Ask for less output, for example fewer items or a smaller count, or split the input.
tool_busy 503 All tool workers are busy Wait a second and try again. Nothing was changed, so retrying is safe.
tool_disabled 503 This tool is switched off Try again later, or look for a related tool at https://setget.net/tools.
tool_failed 500 The tool hit an unexpected problem Try again. If it keeps happening, send the request_id to https://setget.net/feedback so we can find the cause.
tool_daily_limit 429 Daily tool limit reached Wait for the limit to reset. The message says when that is.
storage_off 503 File tools are not switched on Use the tools that work on text input for now, or try again later.
storage_unavailable 503 File storage is temporarily unavailable Try again in a few seconds. Uploads that already finished are not affected.
file_too_large 413 The file is too large Make the file smaller first, for example by compressing or trimming it, then upload it again.
too_many_files 400 Too many files Split the files across more than one drop, or zip them into one file first.
file_not_found 404 That file reference does not point at a file Use the "ref" value returned when the file was uploaded, for example "DROP_ID/f1". Files expire, so upload it again if it is gone.
upload_incomplete 409 The upload has not arrived yet Send the file to its upload URL with PUT first, then try again.
file_refused 422 This kind of file is not accepted Upload documents, images, audio, video, archives or text instead.
unsupported_file 422 This tool cannot read that file Check the tool page for the file types it accepts, and convert the file first if needed.
upload_daily_limit 429 Daily upload limit reached Wait for the limit to reset. The message says when that is.
job_not_found 404 No job has that ID Check the ID. Jobs and their results expire, so run the tool again if it is gone.
job_daily_limit 429 Daily job limit reached Wait for the limit to reset. The message says when that is.
too_many_jobs 429 Too many jobs waiting Wait for one of your jobs to finish, or cancel one, then try again.
jobs_paused 503 File jobs are paused Try again later. Tools that work on text input are not affected.
job_timeout 422 The job took too long Try a smaller or shorter file, or ask for smaller output.
job_out_of_memory 422 The job ran out of memory Try a smaller file. For images, reduce the pixel dimensions first.
job_output_too_large 422 The result is too large Ask for smaller output, for example lower quality, smaller dimensions or fewer files.
worker_lost 503 The worker stopped unexpectedly Run the tool again. If it fails the same way, the file itself may be triggering the problem.
job_cancelled 409 The job was cancelled Run the tool again if you still need the result.
job_failed 500 The job hit an unexpected problem Try again. If it keeps happening, send the job ID to https://setget.net/feedback so we can find the cause.
tool_unavailable 503 This tool is not available on this server Try again later, or look for a related tool at https://setget.net/tools.
pipeline_not_found 404 No pipeline has that ID Check the ID. Pipelines and their results expire, so run it again if it is gone.
too_many_pipelines 429 Too many pipelines running Wait for one of your pipelines to finish, or cancel one, then try again.
pipeline_cancelled 409 The pipeline was cancelled Steps that had already finished keep their results. Run the pipeline again if you still need the rest.
cpu_quota 429 Daily CPU allowance used up Wait for the allowance to reset at 00:00 UTC. The message says how long that is. Tools that work on text are not affected.
invalid_json 400 The request body is not valid JSON Send a JSON object, for example {"input": {"text": "hello"}}, with Content-Type: application/json.
too_large 413 The request is too large Send a smaller request. For big files, upload the file and pass a reference instead of the content.
rate_limited 429 Too many requests Slow down and try again after the number of seconds in the Retry-After header.
daily_limit 429 Daily write limit reached Wait until tomorrow, or reduce how often you write. Reading is not affected.
not_found 404 Nothing is stored there Check the name. Everything on SetGet expires, so create it again if it is gone.
forbidden 403 This credential does not allow that Use the write token for changes, or the password the key was protected with.
unavailable 503 Storage is temporarily unavailable Try again shortly. For a write, check the current state first so the change is not applied twice.
invalid_timing 400 The schedule has no usable time Send one timing field. If the first run is more than a day away, also raise ttl_seconds (at most seven days).
invalid_cron 400 The cron expression is not valid Use five fields (minute, hour, day of month, month, day of week), for example "0 9 * * 1-5", or a macro such as @daily.
invalid_timezone 400 The time zone is not recognised Use a name such as Europe/Oslo or America/New_York. Abbreviations such as CET are not accepted. timezone only applies to cron.
schedule_too_frequent 400 The schedule runs too often Use every_seconds of 60 or more, or a cron expression whose runs are at least a minute apart.
schedule_limit 429 Too many active schedules Delete a schedule you no longer need, or wait for one to finish or expire.
schedule_ended 409 The schedule has already ended Read the schedule to see its last outcome, then create a new one.
deadman_limit 429 Too many armed dead-man switches Delete or disarm a switch you no longer need, or wait for one to expire.
not_armed 409 The switch is not armed If the deadline was missed, the action already ran. The owner can start the switch again with rearm and the write token.
component_not_found 404 The status page has no such component Read the status page to see its component names. Names are case-sensitive.
too_many_components 400 The status page is full Remove a component you no longer need, or create a second status page.
component_bound 409 This component follows a heartbeat Leave status out, or send "heartbeat_id": null to stop following the heartbeat and then set the status.
heartbeat_unreadable 422 That heartbeat cannot be followed Check the heartbeat ID. A protected heartbeat can only be bound when the status page is created, with the heartbeat's own token as the credential.
relay_rate_limited 429 The relay is receiving too many requests Send again after the number of seconds in the Retry-After header. The owner can create a relay with a higher rate_per_minute (at most 600).
browser_refused 403 Requests from web pages are refused Send the request from a server, a script or a command line tool such as curl.
already_submitted 409 These files were already sent Ask the person who gave you the link for a new one if something is missing.
nothing_uploaded 409 No file has arrived yet Choose a file, wait for the upload to finish, then press Send.
file_kind_not_accepted 422 This request does not take that kind of file Send a file of a kind listed on the page, or ask the person who made the request to accept this kind.
form_closed 409 This form is closed Ask the person who gave you the link for a new one if you still need to answer.
already_responded 409 This browser already responded Nothing more is needed. If the answer was wrong, tell the person who sent you the link.
poll_closed 409 This poll is closed The results are on the poll page.
already_voted 409 This browser already voted Nothing more is needed. Votes cannot be changed.
too_many_votes 429 Too many votes from this network address Vote from another network, or ask the person who made the poll to raise max_votes_per_ip.
submission_rate_limit 429 Too many submissions Wait a minute and try again.

Older routes (/set, /get) and some storage errors use codes that are not listed here yet; their messages are described in the errors and limits section of the docs.