problems with detecting batch events, b0.22

[ederenn]

Description

Golem Version: GOLEM Version: 0.21.0+dev162.ge4db14a and later

Golem-Messages version (leave empty if unsure):

Electron version (if used): 0.21.0

OS [e.g. Windows 10 Pro]: Any

Branch (if launched from source): b0.22

Mainnet/Testnet:

Priority label is set to the lowest by default. To setup higher priority please change the label
P0 label is set for Severity-Critical/Effort-easy
P1 label is set for Severity-Critical/Effort-hard
P2 label is set for Severity-Low/ Effort-easy
P3 label is set for Severity-Low/Effort-hard

Description of the issue:

Golem seems to have problems with detecting batch events. Both sides for providers and partially for requestor. Not after every app restart there was batching for finished computations. On providers some of today's incomes are confirmed, some others which were computed earlier are still in awaiting state.

there were 3 nodes connected, 1 linux, 2 windows, all of them were requesting and providing

golem_linux.log
golem_win1.log
golem_win_2.log

Steps To Reproduce

1. Launch Golem
2. Request some tasks
3. Wait for task to finish
4. Restart the app
5. Check logs if there was a batching
6. If batching was fine repeat steps 1-5

Logs and any additional context

might be related
https://github.com/golemfactory/golem/pull/4828

Proposed Solution?

(Optional: What could be a solution for that issue)