Arsenalist

Arsenalist

I have the following in my application.ex:

  def start(_type, _args) do
    children = [
      ...
      {Task.Supervisor, name: Amplify.UpdateMetaAudiencesSupervisor}
    ]
    opts = [strategy: :one_for_one, name: Amplify.Supervisor]
    Supervisor.start_link(children, opts)
  end

Then in my controller method I have:

    Task.Supervisor.async(Amplify.UpdateMetaAudiencesSupervisor, fn ->
      IO.inspect("Inside async") # this prints fine
      Amplify.Context.Audiences.get_audiences() # this makes a DB call
     IO.inspect("After DB call") # never gets printed and no SQL logs 
      end)
    end)

I don’t see any SQL statements being printed for the DB call and even if I put raise "error" inside the get_audiences(), I see no error messages in the logs.

How can I perform DB operations inside a Task.Supervisor (and have them printed to logs)?

Showing Posts 1 to 8

dimitarvp

dimitarvp

Nothing immediately jumps to mind, could you share parts of the Amplify.Context.Audiences.get_audiences() function source?

Arsenalist

Arsenalist OP

Thank you for responding.

Here it is:

  def get_audiences() do
      IO.inspect("this will print")
      Audience
      |> preload([:ad_platform_account, :venues, :participants, :products])
      |> Repo.all()
      |> IO.inspect() # this will not print
  end
kokolegorille

kokolegorille

Is the Repo started when You start your supervisor?

Arsenalist

Arsenalist OP

The supervisor is listed after the Repo, so yes?

    children = [
      AmplifyWeb.Telemetry,
      Amplify.Repo,
      {OpenIDConnect.Worker, Application.get_env(:amplify, :openid_connect_providers)},
      {DNSCluster, query: Application.get_env(:amplify, :dns_cluster_query) || :ignore},
      {Phoenix.PubSub, name: Amplify.PubSub},
      Lapin.Supervisor,
      {Finch, name: Amplify.Finch},
      {Task.Supervisor, name: Amplify.UpdateMetaAudiencesSupervisor},
      AmplifyWeb.Endpoint
    ]

The router.ex has this:

  scope "/public", AmplifyWeb do
    get "/audiences/update", MetaController, :update_meta_audiences
  end
Arsenalist

Arsenalist OP

I got this to work with Task.Supervisor.async_nolink() instead of Task.Supervisor.async() but I’m not fully understanding why that is working for me.

al2o3cr

al2o3cr

My guess: Task.Supervisor.async still links the Task to the calling process - in the case of the controller, that’s the request handler process. When the request finishes, that process exits and the Task is terminated.

Arsenalist

Arsenalist OP

Thank you. That makes sense to me.

dimitarvp

dimitarvp

You are better off having a dedicated supervisor just for these tasks. As @al2o3cr pointed out, you were linking them to the process of the request and that ends quickly very often.

— 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
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
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
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