Interpreting SQL Invalidation (_kgl_debug) trace

Oracle Database 19.10 (RAC 2 node).

We have a report that issues a large SQL statement (~1200 lines, multiple union). This statement takes 20 - 30 seconds to parse in our busy prod environment (and of course, when hard parsing, blocks other instances of the same SQL with "cursor: pin s wait on x). After a recent change to this query (WHERE clause filter change), it has sometimes started experiencing significant hard parsing througout the day (one morning had 700 hard parses in 4 hr period). This SQL is run from a parameterized report and uses bind variables, so we would