Package Edition of Nebula Logger
Managed Package
Package Version of Nebula Logger
v4.19
New Bug Summary
This is a new install in a Sandbox although I am a long time nebula user. In this new sb I started getting error emails:
Logger failed to save 1 Nebula__Log__c records for autoproc@{redacted} (Schema.User ID: {redacted})
Errors:
StatusCode: TRANSFER_REQUIRES_READ, Message: The new owner must have read permission
I've not encountered this with nebula before. We only have one settings rule, an org wide one which sets the log owner to our default workflow user; a system administrator user we called Operational Admin. This user has the Nebula Logger: Admin permission set. Every other user is assigned the Log Creator permission set.
In order to try and help work around this issue I assigned the Log Viewer permission set to all users at which point the error emails stopped, and I could see the occasional log being created with the running user's ownership. I assigned history tracking to the owner field which revealed that on these logs, the owner was being set twice (Platform Integration User is the name of our autoproc):
Whereas those which are correctly assigned to the Log Owner user only set it once:
I'm not able to find a pattern. All the affected users are Standard users and usually their logs are created normally, just the odd occasion where they aren't, so I don't really know what else to look for. Any help would be appreciated as I'd rather not assign all users the Log Viewer permission set.
Package Edition of Nebula Logger
Managed Package
Package Version of Nebula Logger
v4.19
New Bug Summary
This is a new install in a Sandbox although I am a long time nebula user. In this new sb I started getting error emails:
I've not encountered this with nebula before. We only have one settings rule, an org wide one which sets the log owner to our default workflow user; a system administrator user we called Operational Admin. This user has the Nebula Logger: Admin permission set. Every other user is assigned the Log Creator permission set.
In order to try and help work around this issue I assigned the Log Viewer permission set to all users at which point the error emails stopped, and I could see the occasional log being created with the running user's ownership. I assigned history tracking to the owner field which revealed that on these logs, the owner was being set twice (Platform Integration User is the name of our autoproc):
Whereas those which are correctly assigned to the Log Owner user only set it once:
I'm not able to find a pattern. All the affected users are Standard users and usually their logs are created normally, just the odd occasion where they aren't, so I don't really know what else to look for. Any help would be appreciated as I'd rather not assign all users the Log Viewer permission set.