ryanwinchester
(Oban Pro 1.6.0-rc.4)
When I create a sub-workflow, it gets the parent workflow’s put_context
while losing the parent workflows add_cascade additions to context
as well as the sub-workflow’s own put_context
Example of what I am experiencing (simplified):
def foo_workflow do
Workflow.new()
|> Workflow.put_context(%{foo: 1})
|> Workflow.add_cascade(:bar, &get_bar/1)
|> Workflow.add_graft(:baz, &baz_workflow/1)
end
def get_bar(%{}), do: 2
def baz_workflow(%{}) do
Workflow.new()
|> Workflow.put_context(%{banana: "yum"})
|> Workflow.add_cascade(:help, &help/1)
|> Workflow.apply_graft()
|> Oban.insert_all()
:ok
end
def help(%{banana: banana}) do
# this will not match because it has:
#
# %{foo: 1}
#
# but I am expecting to be able to match
# on `:banana` key.
#
# Sometimes `baz_workflow` is used on its own,
# and sometimes as a sub-workflow in `foo_workflow`.
end
Where Next?
Trending in Questions
Other Trending Topics
Latest Oban Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #elixirconf-us
- #ai
- #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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
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 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
Thanks for the report! You’ve hit on some things that should be explained, warned about, or possibly fixed in workflows.
The
contextis pulled from the current workflow, then the parent workflow if nothing was found; they aren’t merged. They certainly could be though. The top level cascade (:bar) could probably be propagated down to the sub-workflow as well.Looking into some fixes and improvements now.
ryanwinchester
Thanks.
My main issue is that the
bar_workflowis sometimes used on its own, and other times as a sub-workflow offoo_workflow.Right now it works fine on its own, but not when used as a sub-workflow.
Propagating parent cascades would solve this case, but it would be nice if
put_contextcalls in sub-workflows were merged into context as well.ryanwinchester
(or if the sub-workflow’s own
put_contextwasn’t ignored, that would also solve my case.)ryanwinchester
or if I could pass other arguments into
add_cascadeor
sorentwo
It wasn’t supposed to be. Just a bug in the query. It’s fixed for the next RC, slated in the next couple of days.