@Menion
Construct functionality so that you can send a TB log without sending the log cache is incorrect. (Border with GC rules).
This is all the more when it's done in the background without a clear action by the user.
E.g.: activity in another cache (inadvertently) sends the TB log from a completely different Offline record.
Bad.
+edit
So, according to the results of my activity (unjustified log on the GC page) I came to the conclusion that not only reload TB sends TB (there is a notice so it is relatively OK). But also LOAD TB! (No Alert!) So LOAD is actually UPLOAD SEND!
If I believed this would ever work smoothly so I suggested to rename the button. But this construction is waiting for further problems. So it does not matter.
Why did you choose this complicated path to a simple result?
Construct functionality so that you can send a TB log without sending the log cache is incorrect. (Border with GC rules).
This is all the more when it's done in the background without a clear action by the user.
E.g.: activity in another cache (inadvertently) sends the TB log from a completely different Offline record.
Bad.
+edit
So, according to the results of my activity (unjustified log on the GC page) I came to the conclusion that not only reload TB sends TB (there is a notice so it is relatively OK). But also LOAD TB! (No Alert!) So LOAD is actually UPLOAD SEND!
If I believed this would ever work smoothly so I suggested to rename the button. But this construction is waiting for further problems. So it does not matter.
Why did you choose this complicated path to a simple result?