SZJX

SZJX

I need to perform some actions when the user leaves a channel (in most cases where they close the tab voluntarily, but there may also be a connection loss/timeout etc.)

According to posts like Phoenix.Presence run some code when user leaves the channel and https://stackoverflow.com/questions/33934029/how-to-detect-if-a-user-left-a-phoenix-channel-due-to-a-network-disconnect, intercepting the "presence_diff" event from Presence seems to be a foolproof way to go, as it should also cover the cases where the connection terminates abnormally.

Strangely, the presence_diff event seems to only be triggered when I track the user via Presence.track (i.e. when the user joins), but not when the user leaves (e.g. when I close my browser tab under dev environment)

Meanwhile, adding a terminate(reason, socket) callback in my channel correctly catches the leave event.

I wonder what could be wrong in my configuration. Or did I not understand the use of Presence correctly?

Example code:

  def join("participant:" <> participant_id, _payload, socket) do
    if socket.assigns.participant_id == participant_id do
      send(self(), :after_participant_join)
      {:ok, socket}
    else
      {:error, %{reason: "unauthorized"}}
    end
  end
  
  def handle_info(:after_participant_join, socket) do
    experiment_id = socket.assigns.experiment_id

    Presence.track(socket, experiment_id, %{
      # keys to track
    })

    # Broadcast something
    # broadcast(socket, ...)
    
    {:noreply, socket}
  end

  intercept(["presence_diff"])

  def handle_out("presence_diff", payload, socket) do
    # Only gets triggered at Presence.track, but not when the connection is closed.
    IO.puts("presence_diff triggered, payload is #{inspect(payload)}")

    leaves = payload.leaves

    for {experiment_id, meta} <- leaves do
      IO.puts("Leave information: #{meta}")
      
      # Do stuffs
    end

    {:noreply, socket}
  end
  
  # This works, however.
  def terminate(reason, socket) do
    IO.puts("terminated. #{inspect(reason)}")

    # Do stuffs.
  end

Showing Posts 1 to 3

SZJX

SZJX OP

OK I think I know what happened: Each "participant:" <> participant_id topic is, as its name suggests, only subscribed to by one participant. Therefore, when that participant quits, nobody is subscribed to the topic whatsoever. Apparently in this case the whole Presence also ceases to function.

This is not really what I expected, as I need to run some cleanup after a participant exits, but under this mechanism, whenever the last participant that’s out there exits, my callback wouldn’t be triggered at all. It appears that Presence is not suitable for this purpose.

michalmuskala

michalmuskala

The issue is that the presence leave event is triggered when the process dies. But the process itself is subscribed to this information, so you can’t really do anything in that process, because it is already dead. If there was a separate process listening for those events, it should work just fine.

SZJX

SZJX OP

I see. Thanks for the reply. I also found a related old thread at How to create a process subscribed to a channel topic to watch the handle_diff events?. Seems that if one wants really foolproof disconnection detection, one’d still need to have an external monitoring process after all then.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews