You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dappflow reports 404 for transactions from indexer.
While executing any transaction using Dappflow interface, most of the time, the response is 404, because the indexer has not caught up. However, after a second or so, if you search for the transaction, it's usually there.
I've seen some slowdown in indexing with recent LocalNet algod/indexer/conduit container images myself, so it's quite possibly that + dappflow not handling it well and waiting for them to appear.
I'll raise the indexer slowdown with the core protocol team and I've pinged dappflow's creator in the discord thread.
Dappflow reports 404 for transactions from indexer.
While executing any transaction using Dappflow interface, most of the time, the response is 404, because the indexer has not caught up. However, after a second or so, if you search for the transaction, it's usually there.
Environment
timestamp: 2024-04-01T10:18:01+00:00
AlgoKit: 2.0.1
AlgoKit Python: 3.12.2 (main, Feb 25 2024, 16:35:05) [GCC 11.4.0] (location: /home/eldar/.local/share/pipx/venvs/algokit)
OS: Linux-5.15.146.1-microsoft-standard-WSL2-x86_64-with-glibc2.35
docker: 25.0.3
docker compose: 2.24.6-desktop.1
git: 2.34.1
python: 3.12.2 (location: /usr/bin/python)
python3: 3.10.12 (location: /usr/bin/python3)
pipx: 1.4.3
poetry: 1.8.2
node: 12.22.9
npm: 8.5.1
Steps to reproduce
Expected behaviour
The transaction information should be returned
Actual behaviour
Dapplow returns 404 for the transition in question.
The text was updated successfully, but these errors were encountered: