Testnet processing accounts keeps going back to zero percent

Sorry for the late reply. Memory constraint could be an issue during the fast catchup especially running sandbox (docker) on Windows. We are working on some memory optimizations and I created a ticket to ensure this 4GB use case supported.

Group Transaction error

There is no enough info to give any advice. Which API are you using? The error is definitely not from algod. Post the relevant code (formatted) and API docs you use.

Survey For Having Add-Ons In Wallets

IMO this is a bad idea. Wallet apps are primary hacking targets, adding ability to run code makes it much easier.

Stateful smartcontract MethodCall fail when using multiple txn with AtomicTransactionComposer

Hello Yaaruu, The error is thrown when a transaction with such ID was seen previously. Please double check you are calling the method with actual different value in asset_id. I think it is quite common when developing an app to re-run an app that sends the same transactions (since there is no different ta...

Algorand Node stop synching after upgrading it to version 3.15.1

Hello Sowna, the messages "trackerDBInitialize database schema version is 9, but algod supports only 6..." indicates you are running quite old algod that does not support the latest changes.

Testnet processing accounts keeps going back to zero percent

@ramdio123 check node.log log file for additional messages around the time it flips from 40% to 0%. Try warning, error, catch terms for grepping. The processing loops restarts in case of errors - it could be a networking issue, decoding error or as Fabrice pointed out a memory issue.

Cannot contact Algorand node: HTTP 400 Bad Request: unable to start catchpoint catchup

The error indicates an attempt to start a fast catchup while another fast catchup was in progress.