The weekly run

The tool runs automatically every Monday at 9:00 in the morning, UTC time, on GitHub — the service that stores the project. You do not have to start it or keep a computer on.

What one run does

1. Checks the Airbnb sign-in first, so a dead session is caught before any time is spent on it.
2. Prices the stays. By default it looks at 13 upcoming weeks, one Friday-to-Wednesday stay per week (5 nights), and loads each watched listing’s page for each of those stays.
3. Recalculates the recommendations for the one-bedroom, season by season.
4. Rewrites the spreadsheet mirror — the Observations and Rate Recommendations tabs.
5. Saves the updated price history back into the project, and prints a health summary.

A run that finishes green has recorded real prices. The tool refuses to finish successfully when almost every listing came back empty — that pattern almost always means the Airbnb sign-in has expired or Airbnb blocked the visit, so the run stops and reports failure instead.

Checking on a run

What you do

1. Open the project’s repository page on github.com and sign in.
2. Click the Actions tab near the top of the page.
3. In the list on the left, click Weekly price scrape.
4. The newest run is at the top of the list. A green check means it recorded prices; a red cross means it stopped.
5. To see why a run stopped, click it, then click the scrape job to read its log. The final lines say what went wrong in plain terms.

If a run is red, the “When something goes wrong” page covers the two usual causes — an expired Airbnb sign-in, and Airbnb blocking the run’s computer.

Starting a run yourself

You can run the scrape at any time without waiting for Monday. The first time the project is set up — and any time the sign-in has just been refreshed — it is worth doing a small run first: one stay instead of thirteen. If one stay comes back with real prices, the setup works; if it fails, you have spent very little and the failure message says what to fix.

What you do

1. Open the project’s repository page on github.com and sign in.
2. Click the Actions tab.
3. Click Weekly price scrape in the list on the left.
4. Click the Run workflow button on the right.
5. In the small form that opens you can adjust three things, or leave them alone for a normal full run:
   • Number of weekly Friday-start stays — how many upcoming weeks to price. Enter 1 for a small test run. The default is 13.
   • Nights per stay — the default is 5.
   • Scrape Holiday/Festival bands instead of weekly blocks — tick this to price one stay per holiday and festival period (Christmas, New Year, and so on) using each period’s own dates, instead of ordinary weeks.
6. Click the green Run workflow button in the form.
7. The run appears at the top of the list within a few seconds. Click it to watch progress; a small test run takes a few minutes.

Please do not run it more often than weekly

Once a week is a deliberately light touch — a couple of hundred page visits with a pause between each one. Running it hourly, or many times a day, is exactly the pattern that gets automated visitors blocked, and would put the Airbnb session at risk. When you need an extra run — after refreshing the sign-in, or before a pricing decision — one manual run is fine. A habit of hammering it is not.