If HARMA co-op fails, ask everyone in the party to update to the same version first. Then identify when the failure happens: at lobby creation, when joining, or after a fight has started. That distinction helps you use the fixes documented for the Early Access build.
Match the version on every machine
The official 0.7.0.17 patch notes say co-op requires matching versions. Ask each player to confirm their update, including the host. Try the lobby once everyone is on the same build. An old demo has its own compatibility limits and should be treated separately.
Read the lobby creation error
The patch adds a message identifying Steam service issues when lobby creation fails. If that message appears, note the error and whether anyone can create a lobby on the same version. This gives you a more specific symptom to investigate than a generic report that multiplayer broke.
Pinpoint a disconnect during play
Version 0.7.0.17 fixes a specific party disconnect that occurred when selecting an ally as a target. If your group remembers that pattern, confirm that all players have the patch. If it still happens on matching versions, record the move, the ally targeted, the encounter and the approximate time.
The patch also addressed unavailable Foresight options briefly appearing to a guest at the Altar. Record that separately if it is the symptom you saw. A temporary incorrect menu choice and a lost network session are two different observations.
FAQ
Do all the players need to update or just the host?
All participants need the same version.
Does a failed lobby always mean a Steam service issue?
The patch identifies Steam service issues when it detects that specific kind of lobby creation failure. Read your actual message before drawing a conclusion.
Does the patch fix every in-game disconnect?
It documents a fix for the disconnect associated with selecting an ally as a target. Capture your version and the exact action if you have a different or recurring issue.