Known bug

Quick answer: For the Wild West Pioneers warehouse not connected bug, when a windmill or another building fails to recognize a nearby warehouse, open the nearest warehouse, remove one worker, then add that worker back. A player confirmed this restored the connection, and a developer recommended the same action for affected buildings. Player fix · Confirmation · Developer reply

Players also call it windmill says it's not connected to a a warehouse even tho it is, the title of the Steam report.

Quick facts

  • Symptom: A windmill or another building stops recognizing its warehouse. Player reports.
  • Where to act: The nearest warehouse. Player fix.
  • Recovery: Remove one warehouse worker and add the worker back. Developer reply.
  • Status: Players confirmed the workaround; a permanent fix is not confirmed yet. Confirmation · Developer reply.

Restore the warehouse connection

Open the nearest warehouse

Select the warehouse nearest the building that reports no connection. The warehouse has worker controls; assigning workers also changes its coverage range. Player fix · Gameplay footage.

Remove and reassign one worker

Remove one worker from that warehouse, then add the worker back. This is the workaround confirmed by a player and recommended by a developer. Player fix · Confirmation · Developer reply.

Check the connection

Recheck the affected building. The warehouse menu can show its connected buildings, giving you another place to verify whether the link is recognized. Gameplay footage.

Warehouse menu showing worker controls and two connected buildings

The original poster suspected an upgraded warehouse might be involved, but that cause is not confirmed yet. If reassigning a worker does not help, check the building against the warehouse's displayed coverage range: the gameplay footage shows that the range changes with staffing. Original report.

FAQ

Related

Status as of September 29, 2026: Reassigning a worker restored the connection for reporting players; the developer shared the issue with the team, but a permanent fix is not confirmed yet. Sources: workaround, player confirmation, developer reply.