Skip to content

Customer Console: Jobs and Artifacts

Use the Customer Console to monitor scraping jobs and inspect artifacts without CLI tooling.

Access and tenant scope

  • Sign in through https://console.scrapenest.com.
  • Select your active organization in the org switcher before viewing jobs.
  • All console job/artifact requests are tenant-scoped through X-Org-Id and protected server-side.

Job dashboard

The dashboard supports:

  • Status filters (queued, running, succeeded, failed)
  • Job type filters (light, standard, stealth)
  • Optional exact job_id filter
  • Pagination and manual refresh

Each row links to a detail view where you can inspect the selected job.

Manual submission playground

Use the playground to submit a job directly from the console:

  1. Choose a worker tier (light, standard, or stealth).
  2. Provide a target_url.
  3. Optionally set timeout and tags.
  4. Submit and open the generated job_id in detail view.

Read-only users can monitor jobs but cannot submit them.

Job detail and artifact viewer

The job detail view provides:

  • Job status and timestamps
  • Artifact metadata (artifact_id, type, size, created time)
  • In-app previews for JSON/text artifacts
  • Inline screenshot/image rendering
  • Download actions via short-lived presigned URLs

Status vs outcome

A job has two separate facts:

  • status - the lifecycle: queued, running, succeeded, or failed. It tells you whether the crawl ran to completion without a system error.
  • outcome - the delivery result: success, blocked, or failed. It tells you whether we actually got the content.

These are independent. A target that answers an anti-bot challenge (for example HTTP 403) produces status = succeeded and outcome = blocked: the crawl ran and captured forensic artifacts (screenshot, HTML, console log), but no target content was delivered. Blocked jobs surface a block object (signal, http_status) on the job resource, and they are never charged - you pay for delivered results, not for proxies. If your jobs keep coming back blocked, try a higher engine tier (stealth) or see Handling anti-bot.

Troubleshooting

Empty job list

  • Confirm you selected the correct organization.
  • Refresh dashboard filters and check page number.
  • Verify your account has job-read permissions for the selected org.

Job detail returns not found

  • Confirm the job_id belongs to your active organization.
  • If the job was just created, wait a moment and refresh.

Artifact preview fails

  • Retry from the job detail page using refresh.
  • Generate a fresh download URL and download directly.
  • If failures persist, contact support with job_id, artifact_id, and timestamp.

Permission denied on submit

  • Your role may be read-only for job creation.
  • Ask an org owner/admin to grant a role with job-create permissions.