-
Notifications
You must be signed in to change notification settings - Fork 18
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
bug: Non-managed package actions grouped with managed package entries #320
Comments
Thanks for reporting this, the shared log will really help 👏🏻 Is the log you shared the full logs as retrieved from the org? because there is no In the meantime I will see what we can do to tighten up the |
Thank for the quick reply. We're the providers for the managed package listed and have had a couple customers reference our package as taking too much time based on the log rollup. The original attached log was the entire log... strangely there are 3 logs generated when I do the update but only 1 contained the managed package lines. The flow as my setup to attempt to reproduce but found I could with the default dupecheck in Salesforce and the flow logged elsewhere. We don't often work with manual update logs, so this may be me not understanding. I've attached all 3. |
The log you shared is a bit weird compared to what I am used to seeing. We sometimes see something similar to this in the skipped section of a log when some entries have been removed, but not normally in a full log. You tend to get
It is this assumption that is causing issues. Basically the log has no indication of what event caused the package entry and without an exit we rely on the surrounding exit events. I have raised an idea to improve the debug log out to make this simpler. I have reproduced this with my own logs and I am going to try improve things for cases like this. |
Summary
When debug logs include ENTERING_MANAGED_PKG, the actions that occur after the managed package are rolled up into the managed package entry. This causes the time in the other actions to appear as though they occurred in the managed package
Steps To Reproduce:
Expected result
The additional automation should appear in it's own block and the managed package should stand alone.
Actual result
In the call tree in log analyzer you'll see the additional automation grouped under the managed package line and the time rolled up to the managed package.
Additional information
Sample debug logs and screenshot of log analyzer attached
VS Code Version: 1.80.0
Log Analyzer Extension Version: 1.6.0
OS and version: macOS 13.4.1 (c) (22F770820d)
apex-07LHr00005Zjt3DMAR.log
The text was updated successfully, but these errors were encountered: