October 12, 2026
Since the August update, work on TexArrest has focused on making the system more reliable: keeping publishing moving, fixing county-specific issues, and strengthening the checks that protect removed records from being published again.
Here is what has changed.
More reliable publishing
We fixed an issue that could leave the upload queue stuck when new records arrived while an earlier batch was finishing. Publishing now handles that handoff more reliably.
We also reduced how often the app rewrites its full local archive during uploads. Records are saved at regular checkpoints and when a batch finishes, reducing unnecessary disk activity. Facebook publishing now waits for WordPress uploads to finish, helping keep the publishing steps in order.
County scraper fixes
- Comal: Improved mugshot downloads by preserving the booking page’s session and refreshing image links when a retry is needed.
- Collin: Improved retry handling when the county search page loads without a usable search form.
- Williamson and Collin: Added checks against the latest published booking before using an automatically suggested starting point, while preserving manually selected backfills.
- Smith: Updated the portal address and handling of older links.
These changes address specific failures in the collection process. County portals can still change or become unavailable, so diagnostics remain part of the workflow.
Stronger removal safeguards
Publishing now requires a fresh sync of the removal-suppression list. We also standardized county-name matching so variations in a county’s name do not weaken those checks.
The goal remains the same: records that have been suppressed should stay out of future publishing runs.
Archive protection and duplicate handling
We strengthened encrypted local archives, made imported duplicate tracking survive restarts, and added record-identity checks before updating or deleting WordPress records. These checks help ensure that an operation applies to the intended booking.
Mobile API improvements
The mobile API received improved pagination, date filtering and sorting, and request throttling. Public results also received tighter checks for unpublished, password-protected, and removed records. Version 0.1.5 was deployed on October 4.
A standalone Windows app
The operator app is now packaged as a directly launchable Windows executable, with its own branded icon and desktop shortcut. Running it no longer requires starting the development environment.
Next up: Arizona automation
On the Arizona side, we built an hourly Maricopa import and AzRested publishing workflow with a persistent queue, retries, and duplicate checks.
This automation has been implemented and tested locally, but it has not been enabled or verified through a live publishing run. That verification is still ahead before we describe it as operational.
Thank you for following TexArrest. The work continues on reliable collection, consistent publishing, and responsible handling of record removals.