Internal + Public

Long jobs, "running" results and aetherwave_get_job

Why AetherWave MCP tools answer within about 45 seconds, what a "running" result means, how aetherwave_get_job follows a job to the end, and how to recover a call that timed out.

Updated 2026-10-04 Developers & API mcpget_jobasynctimeoutrunningpollingrecovery

The 45-second answer

AI chat apps give up on a tool call after about 60 seconds. Video, music and comics routinely take longer. So every AetherWave tool that starts a job waits at most about 45 seconds:

The job is already submitted and paid for at that point, and it saves to your gallery whatever happens to the chat.

Never resubmit a running job. A second submit is a second job and a second charge. Follow the first one with aetherwave_get_job instead.

Following a job: aetherwave_get_job

Pass the taskId and the kind the tool returned. It is free.

kind For
image generate, edit, upscale, reframe and background removal for images
video generate_video
video-edit upscale, reframe and background removal for video
music generate_music
merch-mockup merch_mockup (the task ID is its taskKey)
comic-export comic_export (also pass the projectId)

async and wait

Every long tool takes two switches:

Switch Effect
async: true Start the job and return the task ID at once, without waiting
wait: true Wait for the finished result, up to several minutes. Only for clients that allow tool calls longer than 60 seconds

async: true is the right choice when you are starting several jobs at once, such as one video clip per shot.

Recovering a call that timed out

If the chat reported a timeout, the work kept running and saving on AetherWave's side. Ask the assistant to call aetherwave_get_job with the task ID it was given, or find the result in your gallery at https://aetherwavestudio.com/gallery.html. aetherwave_list_my_creations reads the gallery from inside the chat.

Two exceptions