Filebeat NOT sending all matched log entries

Thanks so much Steffen for the response.
we did some test runs after increasing the max_bytes to 104857600 (100 MB) unfortunately things were same :-(.
btw: patterns, I meant was, matching log lines / entries.
see below the filebeat config settings:

In this test run we were waiting for the single file (65 MB, 342K log entries) to be scanned completely (no log entries were added during the process).
As you see below, the matching records were found and send to Elasticsearch Ingest node roughly 25~30 mins interval. This is all stemmed from a single log file. It took 2hr 25min to scan through this 65MB log file.