2023-07-17 11:45:55 P0383 Filtering records on the main thread!
2023-07-17 11:45:55 P0383 Filtering records on the main thread!
2023-07-17 11:45:56 P1046 Filtering records on the main thread!
2023-07-17 11:45:56 P0383 Filtering records on the main thread!
2023-07-17 11:45:57 P0525 Filtering records on the main thread!
2023-07-17 11:45:57 P0383 Filtering records on the main thread!
2023-07-17 11:46:01 P0525 Filtering records on the main thread!
2023-07-17 11:46:01 P0525 Filtering records on the main thread!
2023-07-17 11:46:01 P0525 Filtering records on the main thread!
2023-07-17 11:46:03 P0221 Filtering records on the main thread!
2023-07-17 11:46:03 P0221 Filtering records on the main thread!
2023-07-17 11:46:04 P0221 Filtering records on the main thread!
2023-07-17 11:46:04 P1046 Filtering records on the main thread!
2023-07-17 11:46:04 P0221 Filtering records on the main thread!
2023-07-17 11:46:05 P0525 Filtering records on the main thread!
2023-07-17 11:46:05 P0489 Filtering records on the main thread!
2023-07-17 11:46:05 P0221 Filtering records on the main thread!
2023-07-17 11:46:05 P0221 Filtering records on the main thread!
2023-07-17 11:46:06 P0221 Filtering records on the main thread!
2023-07-17 11:46:06 P0221 Filtering records on the main thread!
and the customer feel it is affecting the performance of the system.
what is the cause of it and how can fix it?
Hi, Paul.
Sounds like you're talking about REST API. And that your are overwriting data with older values if B managed to read record before A finished to update it. Classic conflict resolution ...