Nimble tasks results 404 - use per-page task ids from crawl status, not the crawl id

TL;DR

A 404 from nimble tasks results usually means you passed the crawl id instead of a task id. Crawls are two-level: nimble crawl status --id [crawl-id] returns per-page task ids (task-456, task-789), and nimble tasks results --task-id only accepts those.

Fix

1. A 404 from nimble tasks results usually means you passed the crawl id instead of a task id. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Nimble tasks results 404 - use per-page task ids from crawl status, not the crawl id.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md.

Variant phrasings

Nimble tasks results 404 - use per-page task ids from crawl status, not the crawl id

Why it happens

Nimble's own error-handling reference (nimbleway/agent-skills, error-handling.md): '404 from nimble tasks results' is caused by using the crawlid instead of taskid - use the per-page task_ids from nimble crawl status, not the crawl job id. Related: crawl status may misreport task statuses as failed when they succeeded, so always try nimble tasks results --task-id before assuming failure.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md

Source: Nimble's own error-handling reference (nimbleway/agent-skills, error-handling.md): '404 from nimble tasks results' is caused by using the crawlid instead of taskid - use the per-page task_ids from nimble crawl status, not the crawl job id. Related: crawl status may misreport task statuses as failed when they succeeded, so always try nimble tasks results --task-id before assuming failure.

Verified resolution: A 404 from nimble tasks results usually means you passed the crawl id instead of a task id. Crawls are two-level: nimble crawl status --id [crawl-id] returns per-page task ids (task-456, task-789), and nimble tasks results --task-id only accepts those. Pass the crawl id and you get a 404. And do not trust 'failed' in crawl status blindly - the reference says it occasionally misreports succeeded tasks as failed, so always try fetching the task results anyway before treating it as a failure.

Source URL: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md