I’m developing process automation using oban, but lately I’m facing a problem with updating the code in worker modules. Whenever I update the module for the worker and start the application, the worker keeps processing jobs as if the code hasn’t been updated. In the worker module, even if I comment…

updating: Running oban tests using iex in dev: iex> Oban.Worker.from_string("Oban.Integration.Worker") {:ok, Oban.Integration.Worker} iex> defmodule NotAWorker, do: [] ...> Oban.Worker.from_string("NotAWorker") {:error, %RuntimeError{message: "module is not a worker: NotAWorker"}} ie…

It seems like you’re experiencing a combination of multiple versions of a module in memory, and lingering data in the database. Is it possible you have another app instance running somewhere?

There are no instances running in the background. Running via docker or locally without the docker, is the same problem. The only thing that works is updating the crontab. Do you have any test suggestions I can do to check if it’s something in the app’s startup config? Ty!

There isn’t anything in the config or worker definitions that would prevent code reloading. As far as Oban knows, the worker is a string that represents a module name. When the job executes it looks up the module name and executes the job—the module definition isn’t stored in the database.

Can you call the perform/1 function directly from a test to ensure that it works as intended?

Lately I’ve had an error with it a bit similar, after many executions of jobs it stops showing any debug messages for me, but the work runs normally, this in my dev environment, in production it doesn’t happen.

[image] gabriel137: Lately I’ve had an error with it a bit similar, after many executions of jobs it stops showing any debug messages for me, but the work runs normally This sounds like the telemetry handler for logging gets detached in development. There will be a warning in your logs statin…

That’s strange. As a workaround you can always delete the _build directory (or just _build/dev/lib/myapp). Also you can call :code.which(MyWorker) to retrieve the beam file for your module so you could check the modification time of this file, or load it in an iex session to check stuff.

[image] osmirbresciani: I’m developing process automation using oban Curious to find out more what you’re building. We are also starting a process automation project soon. Would appreciate if you drop me a message.

I will observe, thanks for the reply.

Elixir Programming Language Forum

Problem with Oban Workers

Questions & Help Questions

osmirbresciani November 10, 2021, 11:48am 6

Yes, it works. The “bug” appears when running mix phx.server with MIX_ENV=dev