Skip to content

Fix job ID detection to support UUID v7#19

Merged
abimaelmartell merged 1 commit intomainfrom
fix/uuid-v7-job-id
Jan 31, 2026
Merged

Fix job ID detection to support UUID v7#19
abimaelmartell merged 1 commit intomainfrom
fix/uuid-v7-job-id

Conversation

@abimaelmartell
Copy link
Copy Markdown
Member

@abimaelmartell abimaelmartell commented Jan 31, 2026

Summary

  • Update UUID regex to accept any UUID format, not just v4
  • Firecrawl returns UUID v7 job IDs which were incorrectly rejected

Problem

# Start a crawl
firecrawl crawl https://docs.firecrawl.dev --limit 5 -o job.json

# Try to check status with the returned job ID
firecrawl crawl 019c0ed5-126b-7581-90f1-894a349a1e9d
# Error: URL must have a valid top-level domain or be a valid path

The job ID 019c0ed5-126b-7581-90f1-894a349a1e9d is UUID v7 (third segment starts with 7), but the regex only matched UUID v4 (third segment must start with 4).

Test plan

  • Unit tests updated and passing
  • Manual test: firecrawl crawl <uuid-v7-job-id> returns status

Fixes #14

Firecrawl returns UUID v7 job IDs, but the regex only matched UUID v4.
This caused `firecrawl crawl <job-id>` to fail with a URL validation error
instead of checking job status.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@abimaelmartell abimaelmartell merged commit 96d0786 into main Jan 31, 2026
1 check passed
@abimaelmartell abimaelmartell deleted the fix/uuid-v7-job-id branch January 31, 2026 00:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI rejects job ID when checking crawl status

1 participant