lessless
I have this challenge of importing (downloading and saving) paginate data.
Currently I’m doing it recursively in a workflow step and I think it’s safe because if it will crash (f. ex. due to remote api error).
I designed this code to resume from the last known transaction on the first fetch, so it should also resume from the last saved transaction in a case of a crash
def insert(account_id) do
Workflow.new()
|> Workflow.put_context(%{account_id: account_id})
|> Workflow.add_cascade(:trigger_sync, &trigger_sync/1, queue: :transactions_sync)
|> Workflow.add_cascade(:import, &import_txs/1,
deps: [:trigger_sync],
queue: :transactions_sync
)
|> Oban.insert_all()
end
def import_txs(%{account_id: account_id}) do
account = BankAccount.by_id(account_id)
import_txs(account.finexer_id, account)
end
def import_txs(%{paging: %{next: nil}}, _account) do
:ok
end
def import_txs(source, account) do
{:ok, txs_resp} = download_transactions(source, account)
{_, _} = save_transactions(txs_resp, account)
import_txs(txs_resp, account)
end
def download_transactions(finexer_id, account) when is_binary(finexer_id) do
APIClient.account_transactions(finexer_id, [{:"timestamp.gte", Transaction.account_checkpoint(account_id)}])
end
def download_transactions(txs_resp, _account) when is_map(txs_resp) do
APIClient.account_transactions(txs_resp, :next_page)
end
defp save_transactions(txs_resp, account) do
txs_resp
|> Map.get(:data)
|> Transaction.bulk_import(account)
end
As a matter of curiosity I wonder if workflows design can support replacing downloading paginated data by dynamically adding jobs.
For example import_txs can import first page, check if there is more (txs_resp.page.next != nil) and then schedule next job with %{source: txs_resp.page.next} as an argument.
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
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
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
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
That design should work. There’s no “finished” state for a workflow, so you can always append another job. Did you give that a try?
lessless
I haven’t yet. I just don’t have enough understanding of Oban to put together a working solution.
I guess the shortest path to that would be to call
add_cascadeinstead ofimport_txsinsideimport_txs/2.So the last function would import the current page and schedule the next job. But how do I pass
txs_respto the next job?