-
-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.LimitException: Regex too complicated from LogEntryEventBuilder.applyDataMaskRules: #639
Comments
Hi @EnglundAndreas - do you know how long the string is that you're logging? And which parameters are you providing to |
It should be about 35 000 characters, I'm serializing the scope from the batchjob as a JSON so it's a bit string. I have an abstract custom Retry class that I'm using to log errors and be able to retry them from the error record. Here is the method that logs the error, where "this" is the class that
This is the class that is being serialized (the properties is variables that I use to rerun the method on errors):
Since the scope of the batch with a size of 200, although only contains Ids, it still becomes a long string. So understandable that the logger does not support these big error messages. |
@EnglundAndreas thank you! This is really helpful info to have. I'm not sure how much I'll be able to optimize the regex for data masking, but I'll plan to do some analysis & testing to see what's possible. |
Package Edition of Nebula Logger
Unlocked Package
Package Version of Nebula Logger
v4.12
New Bug Summary
I get an expected error when running a batch + queuable job due to locking error from a Query. So I have Nebula Logger that I want to log this error, but when it's trying to log my original error, I get an exception "System.LimitException: Regex too complicated".
Stack Trace from Nebula Logger (error is LogEntryEventBuilder.applyDataMaskRules):
Class.LogEntryEventBuilder.applyDataMaskRules: line 928, column 1
Class.LogEntryEventBuilder.setMessage: line 151, column 1
Class.Logger.error: line 838, column 1
The text was updated successfully, but these errors were encountered: