- Pharos Product Updates
- Posts
- Pharos Maintenance Release (1.850.56) is Live in Production!
Pharos Maintenance Release (1.850.56) is Live in Production!
Your production instance has been successfully upgraded on January 10th, 2025
Pharos Hermes
January 11, 2025
Upgrade Completed!
If you are receiving this notification your production org has been successfully upgraded to the latest maintenance release. For more details please refer to our release schedule published on Pharos Support Portal.
Reporting Issues
While we constantly perform rigorous testing of our application during all stages of development, we simply cannot test in your org. Each Salesforce organization is unique in its configuration and usage. Therefore, It is important to double check your Logs tab as soon as you can!
Note: Timing is key. If you were experiencing issues before the date of this upgrade, they’re likely unrelated to the upgrade itself. We still want to hear about them, but understanding the context will help us address your concerns more efficiently.
Things to look out for
Pharos errors — these are Logs with Pharos Category. These indicate potential problems with the Pharos managed package. If you started seeing these errors after the upgrade, do let us know!
Incomplete data on Log or Issue records. If you notice something is missing in your logs post upgrade, such as: lack of visual debug views, lack of environment data, or even lack of log records themselves, definitely let us know!
Broken integrations. If you notice lack of notifications, Jira/ADO tickets, or changes in your GitHub change tracking repository post upgrade, please give us a holler!
Any other issues. The list above reflects the most common problems our customers may face. It is by no means exhaustive, however. If you are unsure whether the problem you started seeing is upgrade related, let us know anyway and we’ll help you investigate.
How to report problems
Send an email to [email protected] providing your Salesforce Organization Id, any screenshots or necessary details in the email. Please also include Maintenance Release in the subject.
Create a case via our support portal with any screenshots or details, as well as the following information:
Release Notes
Pharos maintenance releases typically address known or reported bugs. However, we will sometimes include small functionality enhancements as well.
Bugfixes
Errors on cache item over 100K (LOG-2311)
Unable to select Github repository due to an error (LOG-2306)
Failed broadcast keeps retrying and going into an endless loop (LOG-2310)
Unable to see the context tab in some flow logs (LOG-2312)
Transform element: tooltip UI issue in flow debug view (LOG-2281)
Flow Debug View: path overlapping starting flow element (LOG-2268)
Debug view (Integration log): The last line is overlapped on Body tab. (LOG-2273)
Incorrect font used to display impact report data on Windows (LOG-2249)
Error occurs when saving Jira Defaults settings from Admin (LOG-2323)
JIRA Integration: Switching from Cloud to Hosted JIRA fails (LOG-2307)
Jira tickets created for older issues (LOG-2304)
Create Ticket (on Log, Issue): Issue with 'Complete the Form' option (LOG-2275)
Create Ticket (on Log, Issue): Ticketing Action forms are not displayed when a user changes values in the 'Send action to' field (LOG-2274)
Create Ticket (on Log, Issue). The Subject field does not display changes made in JIRA Ticketing Action. (LOG-2272)
Event Record Lightning Page is not assigned as Org Default (LOG-2328)
Donut charts on event details are not showing correctly (LOG-2321)
Intermittent Pharos errors for some monitoring rules (LOG-2314)
Non-salesforce object ids are mislabeled as related objects (LOG-2329)
Error on very large issues processing. Too many query rows: 50001 (LOG-2320)
Pharos error on very large issues with lots of related records. Related Objects: data value too large (LOG-2317)
Trace Schedule - trace calendar on list view not show correctly (LOG-2254)
Attempt to de-reference a null object when processing Bulk API results (LOG-2340)
Charts on Event don't show correct information (LOG-2339)
Failed to create Log for Inbound Email: FlowExceptionParser: Attempt to de-reference a null object (LOG-2318)
Enhancements
Remove ticket link from Issue when ticket is removed in Jira or Azure DevOps (LOG-2260)
Add full error message to pharos log details if inbound email fails to create a log (LOG-2271)
Updated color scheme for showing related issues on occurrence chart (LOG-2022)
Adjust ticket linking/duplication logic (LOG-2244)
Don’t show Event Log Records tab on Archival Event layout (LOG-2216)