DynamicSupervisor starting child with more than one argument

Yes, exactly. The preference should be to use start_link/1. This requires you to pass everything as an option. Use Keyword.fetch!/2 for required fields. This way you can use the “tuple child specifications”.

If for some reason that is not possible and really can’t be made possible, then use the map version.

The faster everyone standardizes on start_link/1, the sooner the problem will disappear. :slight_smile: