14:37:03 <foxett> Hello. I need help. For some reason I receive one transaction out of several using the Wallet RPC get_transfers method
14:42:29 <m-relay> <j​effro256:monero.social> Can you provide more information, please? What does `wallet2::get_transfers` return versus the RPC endpoint that you're missing? What kind of transactions are they? What kind of wallet? Which calls exactly did you make before this? Do you have logs? You really haven't explained what expected behavior you're looking for or what you've tried already which makes it hard for people to help you.
14:52:16 <foxett> i'm sorry. https://pastebin.com/iSKpCh2W link for request and response from postman. I receive one (first) transaction although monero gui shows correctly from the same node - 2 transactions
14:53:22 <m-relay> <j​effro256:monero.social> Was the second transaction still in the pool?
14:53:38 <m-relay> <j​effro256:monero.social> `get_transfers` only returns confirmed transactions
14:55:29 <foxett> The second transactions The second transaction already has 523 confirmations. Tell me how I can show you the logs of the second transaction from the monero gui?
14:55:41 <foxett> The second transaction already has 523 confirmations. Tell me how I can show you the logs of the second transaction from the monero gui?
14:56:27 <foxett> The second transaction id: 4b5971a135f92ab939dc36715fec869fa90292befc6dd34dcdef294028e91650
14:58:09 <m-relay> <o​frnxmr:xmr.mx> Are all transfers going to the same account?
14:59:38 <m-relay> <j​effro256:monero.social> Yes, the `account_index` parameter you send in the request must match the subaddress account index of the received transfer that you're expecting in the responde
14:59:42 <foxett> yes. One wallet, one account, several addresses
15:01:02 <foxett> I tried with it and tried without it at all. The result is the same. At the same time, Wallet GUI displays everything correctly. Both transactions were sent to the same address.
15:07:57 <m-relay> <j​effro256:monero.social> Is it returned with the `incoming_transfers` RPC endpoint?
15:11:47 <foxett> No. ( https://pastebin.com/nc4yGm5G
15:12:10 <foxett> First transaction only
15:15:59 <m-relay> <o​frnxmr:xmr.mx> Using the exact params that you sent, returned multiple transactions for me
15:16:22 <m-relay> <r​ajafan:xmr.se> what is the average commission for xmr withdrawal?
15:20:17 <m-relay> <o​frnxmr:xmr.mx> plowsof
15:20:57 <foxett> When requesting a balance through the RPC, I also see a balance that takes into account only the first transaction
15:21:02 <m-relay> <j​effro256:monero.social> Commission from whom ?
15:21:20 <m-relay> <o​frnxmr:xmr.mx> Yes, connected to my own node and my own wallet
15:21:37 <m-relay> <o​frnxmr:xmr.mx> Bro keeps posting nonsense in here
15:22:44 <foxett> What could be wrong with me?
15:23:11 <m-relay> <o​frnxmr:xmr.mx> the wallet file that your using might not be synced?
15:23:32 <m-relay> <o​frnxmr:xmr.mx> You're*
15:23:45 <m-relay> <j​effro256:monero.social> Is it different wallet cache files ?
15:24:09 <m-relay> <r​ajafan:xmr.se> for withdrawal via automatic system
15:24:34 <m-relay> <j​effro256:monero.social> What automatic system blud
15:25:48 <foxett> {
15:25:48 <foxett>     "id": "0",
15:25:49 <foxett>     "jsonrpc": "2.0",
15:25:49 <foxett>     "result": {
15:25:50 <foxett>         "height": 3400501
15:25:50 <foxett>     }
15:25:51 <foxett> }
15:26:24 <foxett> It seems to be less than a block with a transaction
15:26:35 <plowsof> Rajafan form a coherent question in another channel as this is likely not dev related 
15:27:02 <m-relay> <j​effro256:monero.social> Yeah that height is ~1000 blocks behind
15:27:08 <foxett> I did get_height correctly to get the current sync block of the wallet?
15:27:11 <m-relay> <o​frnxmr:xmr.mx> The same nameless one he's been asking about posting on getmonero for 6 months
15:27:37 <m-relay> <o​frnxmr:xmr.mx> Foxett, yes, but your wallet isnt synced
15:28:41 <m-relay> <o​frnxmr:xmr.mx> Same one he posted screenshots here about
15:29:16 <foxett> Thank you very much guys. Can you tell me if I can run synchronization by request or do I need to contact DevOps to run it on the server?
15:29:25 <m-relay> <o​frnxmr:xmr.mx> Tldr: its unrelated to monero-dev , monero-site, etc.
15:29:48 <m-relay> <o​frnxmr:xmr.mx> You just need to connect the wallet to a daemon and let it sync
15:30:29 <m-relay> <j​effro256:monero.social> Foxett, you can call the "refresh" command on the RPC wallet  as long as it has an assigned daemon
15:31:09 <m-relay> <j​effro256:monero.social> If it doesn't have an assigned daemon , you can assign one by URL using the "set_daemon" command
15:33:47 <foxett> Thank you guys. Sorry for my English. I am writing through a translator.
15:35:28 <m-relay> <j​effro256:monero.social> That's okay! I'm glad ofrn could figure it out lol
15:35:44 <m-relay> <j​effro256:monero.social> It's always a syncing issue isn't it
15:41:59 <foxett> after refresh when I request get height I get different values ​​every time but sometimes they become bigger sometimes smaller but they repeat all the time. What could it be? That is, it does not catch up with the node
15:43:48 <m-relay> <o​frnxmr:xmr.mx> are you using v0.18.4.0?
15:45:48 <foxett> "version": "0.18.3.4-release",
15:47:10 <m-relay> <o​frnxmr:xmr.mx> Update to 18.4.0
15:47:52 <foxett> Thank you. I asked DevOps to do it already.
15:49:24 <m-relay> <o​frnxmr:xmr.mx> the get_height should only be increasing. Is the wallet being closed periodically? There is a bug that will lose the wallet state if closed
15:51:28 <m-relay> <o​frnxmr:xmr.mx> Lets continue in #monero-support
15:53:15 <foxett> I understand that it should increase after node blocks, but it runs in circles between some values. Maybe RPC Wallet needs to be restarted? There are no errors. Try closing and opening the wallet?