Crowdhailer
When starting a process under supervision the supervisor is given a start function for the child.
This start function must return one of the following.
{:ok, pid}{:ok, pid, term}:ignore{:error, reason}
I’m trying to find examples for all the reason you might have a process fail to start.
The reasons I have found so far are.
- Invalid configuration
For example a database that takes a url as start argument but the string might not be a valid database url.
DB.start_link(url: "!I'm no url")
-
Unavailable external service
When starting a process if it cannot connect to a required resource then the pid fails to start. Again failing to connect to a database is an example of this. -
Process name is already taken
Process can be started with Atom names, if the name is already taken the process would fail to start.
If you can think of any additions to this list I would greatly appreciate them. Examples would be even more awesome, thank you. 
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lpil
I’ve sometimes used
ignorewhen I don’t want a subsystem to run, for example debugging code used in development.wolf4earth
We have something similar. A part of our app is exchangeable via configuration and using a behavior. Certain implementations require an additional supervision tree, while others do not.
In that scenario
initis an optional callback, where we fallback on:ignoreas a default if not implemented.Crowdhailer
So the only thing missing from my original list was an ignore option.
With this feedback I am certainly up for trying some supervisor designs which do not allow a process to fail at startup. i.e.
start -> {:ok, pid}becomesstart -> pidI think external service checking should not be done in the init callback of a Gen_* process.
And for now I think I have another approach to naming.