Backend: POST /competitors/scrape/scheduled triggers run_scheduled_booking_scrape in a background task — repopulates the queue with today's high/medium/low priority dates and processes it. Returns 400 if scraper is disabled, 409 if already running. Frontend: button in the Automatic Schedule card to trigger the scheduled job manually (useful after an interrupted overnight run). Manual Scrape description now shows which backend mode is active (hotel-page vs search-results) so it's clear what the date range scrape actually does. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| jobs | ||
| services | ||
| auth.py | ||
| database.py | ||
| Dockerfile | ||
| main.py | ||
| migrate_direct_data.py | ||
| requirements.txt | ||
| scheduler.py | ||
| schema.sql | ||