Transaction Limits in Apex are only working for CPU and Heap Size on Managed Package version

[alan-turpin]

I have been trying to capture transaction limits inside an Apex class to monitor how many SOQL queries are being used in my transaction, however they are always coming back with 0.

Here is a sample Apex class that should use 50 SOQL queries

public with sharing class SoqlQueryDemo {
    
    @InvocableMethod(
        label='Run SOQL Query Demo' 
        description='Executes 50 SOQL queries and logs the count'
    )
    public static void run() {
    
        for (Integer i = 0; i < 50; i++) {
            Account acc = [SELECT Id, Name FROM Account LIMIT 1];
        }
        
        Integer totalQueries = Limits.getQueries();
        Nebula.Logger.info('Number of queries ' + totalQueries);
        
        Nebula.Logger.saveLog();
        
    }
}

The test logged in the info state shows 50 queries used but on the transaction limits page it shows 0:

I have tried calling this class from a trigger, in a flow and anonymous apex and they all do the same thing.

Whenever I configure a flow that uses the built in log entry action, it captures the soql queries used in the flow, but not this Apex class.

I have confirmed that I have the Logger Admin permissions and can run soql queries to get the data directly from the SObjects (they show 0 used and 100 max, showing that it is getting and saving information).

Nebula Logger Version 4.16.0 (managed package)

Confirmed that an unlocked package (4.16.5), this works as expected.

What am I doing wrong? Is there a gap in my knowledge on how this is meant to function?