NickTomlin
I’m attempting to add quantum to a phx.new project and encountering the following compiler error:
== Compilation error in file lib/quantum_phoenix/scheduler.ex ==
** (CompileError) lib/quantum_phoenix/scheduler.ex:2: Crontab.CronExpression.__struct__/0 is undefined, cannot expand struct Crontab.Cr
onExpression
(stdlib) lists.erl:1354: :lists.mapfoldl/3
lib/quantum_phoenix/scheduler.ex:2: (module)
(stdlib) erl_eval.erl:670: :erl_eval.do_apply/6
(elixir) lib/kernel/parallel_compiler.ex:198: anonymous fn/4 in Kernel.ParallelCompiler.spawn_workers/6
My application (lib/quantum_phoenix/application.ex):
defmodule QuantumPhoenix.Application do
use Application
def start(_type, _args) do
import Supervisor.Spec
children = [
supervisor(QuantumPhoenix.Repo, []),
supervisor(QuantumPhoenixWeb.Endpoint, []),
worker(QuantumPhoenix.Scheduler, []),
]
opts = [strategy: :one_for_one, name: QuantumPhoenix.Supervisor]
Supervisor.start_link(children, opts)
end
def config_change(changed, _new, removed) do
QuantumPhoenixWeb.Endpoint.config_change(changed, removed)
:ok
end
end
My quantum scheduler (lib/quantum_phoenix/scheduler.ex):
defmodule QuantumPhoenix.Scheduler do
use Quantum.Scheduler, otp_app: :quantum_phoenix
end
And my config/dev.exs:
# ... all the phx.new defaults
config :quantum_phoenix, QuantumPhoenix.Scheduler,
jobs: [
phoenix_job: [
schedule: "*/2 * * * *",
task: {QuantumPhoenix.Task, :work, []},
]
]
I am using Phoenix 1.3.0 and elixir 1.6.1/OTP 20.
From what I understand (which is not much since i’m new to Elixir and Phoenix), this error typically involves trying to reference a namespaced module without specifying the full namespace. I can’t find anywhere in my own code where I’m incorrectly namespacing things so my assumption is that this is an issue how my phoenix project is interacting with Quantum. I have a similar setup in an on Phoenix project that compiles just fine.
Trending in Questions
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
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
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Just published claude-code-elixir, a plugin marketplace for Claude Code with Elixir support. These are the plugins I’ve been using for my...
New
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
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Hmm I’m using it just fine on Elixir 1.6.1.
And Phoenix really should have absolutely nothing to do with this (so I’m fixing up the title). ^.^
This sounds most to me like a corrupt
_builddirectory, wipe it and try again? If that still happens then minimize the issue and post is a public git repo after it is minimized.NickTomlin
Blowing away
_buildseems to have done the trick. Thanks!As I said, i’m new to elixir and phoenix, what is the typical reason behind something like this? All I did was do a
phx.newand then add quantum andmix deps.get? (i’m happy to post that as an additional question if it’s preferred).OvermindDL1
I only ever see it happen in two cases:
^.^;