MIXED_DML_OPERATION Error in NebulaLogger Tests with User Trigger

[Norema9]

Hi! We have been using a NebulaLogger for a while without any issues. However, when we create a trigger on User that inserts a GroupMember, the LogEntryEventHandler_Tests and LogHandler_Tests fail with a MIXED_DML_OPERATION error. It appears that when a loggerScenarioOwner user is inserted in the test method, it triggers our process that attempts to insert a GroupMember (a setup object) and the test method that tries to insert a LoggerScenario__c (a non-setup object). This results in a DML operation on both setup and non-setup objects in the same transaction.

Here is the list of tests involved and where the similar issue occurs:

- LogEntryEventHandler_Tests.it_should_set_logger_scenario_owner_as_log_owner_when_log_assignment_enabled_via_logger_scenario_rule
- LogHandler_Tests.it_should_set_owner_when_default_configured_with_user_id
- LogHandler_Tests.it_should_set_owner_when_default_configured_with_username

I wanted to know if there are any upcoming adjustments on your side regarding these tests. Thank you in advance for you assitance !

Cc @angelikagalang

System.DmlException: Insert failed. First exception on row 0; first error: MIXED_DML_OPERATION, DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): LoggerScenario__c, original object: GroupMember: []
Class.LogEntryEventHandler_Tests.it_should_set_logger_scenario_owner_as_log_owner_when_log_assignment_enabled_via_logger_scenario_rule: line 653, column 1

[jongpie]

Hi @Norema9 - I can try to look into this more in the coming weeks to see if there's a way to avoid these kinds of errors. Could you possibly provide me with a small sample Apex trigger that shows how you're creating the GroupMember records in your User trigger? Is it just a "normal" insert DML statement, or are you using any kind of async approach for the insert statement (queueable, @future, etc.)?

[jongpie]

@Norema9 thanks so much for the details! This is really helpful context. I looked into this a bit, and offhand, I think I can handle this on my side - the failing tests can probably be rewritten so that they don't need to create a user (or if there's no way to do that, I'll keep those specific tests only in Nebula Logger's pipeline, and will exclude them in the package itself so they don't cause failures in orgs like yours).

I don't have a specific timeline on when I'll fix this (I haven't had much time for open source work the last 3-4 months), but I'll try to make this one of the first things I work on once I have some time to work on Nebula Logger.

[jongpie]

FYI I've made issue #938 to track my progress on this.

[Norema9]

@jongpie thank you for your understanding and for addressing this issue! I am glad the context was helpful. It is great to hear that you plan to manage the failing tests on your side, I truly appreciate your flexibility.

I understand that time can be limited, so whenever you have chance to work on it, I will remake the test. If you need any assistance or additional context from my end, don't hesitate to reach out.

Thanks once again !

[jongpie]

This issue should now be resolved in release v4.19.3 🥳

If anyone runs into more issues related to this, please let me know!