Automation · Tulsa, OK
What is stale
This chapter refreshes itself on a weekly timer: it pulls new agendas and meeting video from Tulsa's portal, re-checks every external link on the site, and rebuilds the search index. This page reports what actually happened, including when it failed.
A site that quietly rots looks identical to one that is current, right up until somebody relies on it. So the status below is generated by the jobs themselves — it is not maintained by hand and cannot be made to look better than it is.
Status
Loading the last run…
| Job | What it does | Last run | Result | Detail |
|---|---|---|---|---|
| Loading… | ||||
What each job is allowed to do
- Agendas and meetings. Fetches only documents Tulsa has already published, from Granicus at https://tulsa-ok.granicus.com/ViewPublisher.php?view_id=4. It never logs in, never submits anything, and never touches a page the city has not made public.
- Link check. Re-fetches every external link this chapter publishes. Cities move pages, and a records-request link that 404s fails a reader at the exact moment they were about to act.
- Search index. Rebuilds the site's index from the pages and the extracted agenda text, so a resident can search a phrase and land on the agenda that carried it.
- Nothing writes to a government system. Records requests are sent by a person, deliberately, never by a timer.
If a job has been red for a while
That is a bug, not a policy. Tell us — the whole point of publishing this page is that somebody outside the project can see the failure before we do.