Missing processes when started with DynamicSupervisor

That is exactly right, thank you so much @axelson !!!

One more step in my learning Elixir journey

You need to change that line to GenServer.start_link(__MODULE__, nil) so that your process is linked to the supervisor.

The start_link/1 function must return {:ok, pid} where pid is the process identifier of a new process that is linked to the supervisor.

from: Supervisor — Elixir v1.20.2

Can you please elaborate on that? On the old code that I had, using Supervisor and :simple_one_for_one strategy they showed up on the tree, only after converting to DynamicSupervisor I do not found them on the tree anymore..

Sure @axelson , start_child returns a pid as expected and everything seems to be working fine, all the childs launched this way work without a problem. I just don’t see them on the observer application tree…

This is the Hangman.Server code:

defmodule Hangman.Server do
  alias Hangman.Game
  use GenServer

  def start_link(_) do
    GenServer.start(__MODULE__, nil)
  end

  def init(_) do
    {:ok, Game.new_game()}
  end

  def handle_call({:make_move, guess}, _from, game) do
    {game, tally} = Game.make_move(game, guess)
    {:reply, tally, game}
  end

  def handle_call({:tally}, _from, game) do
    {:reply, Game.tally(game), game}
  end
end

And this is my application entry point:

defmodule Hangman.Application do
  use Application

  def start(_type, _args) do
    options = [
      name: Hangman.Supervisor,
      strategy: :one_for_one
    ]

    DynamicSupervisor.start_link(options)
  end
end

I think you may have something wrong in your Child specification. From the start_child docs:

child_spec should be a valid child specification as detailed in the “Child specification” section of the documentation for Supervisor. The child process will be started as defined in the child specification.

Can you show your Hangman.Server code? Also what is the return value of start_child?

Well they are not separate apps, so that’s quite logical.