Pharos 2.284.1 maintenance release

Maintenance release for orgs on Pharos 2.0.

Bug fixes

• Errors whose Salesforce message is in a language other than English group into a single issue, and their notification emails are sentIssue TrackerLOG-2948Docs
• Standard Salesforce errors show their correct namespace instead of "unknown"Error TrackingLOG-2949Docs
• Very large flow error emails are accepted and loggedError TrackingLOG-2957Docs

Enhancements

• System Overview can take snapshots of your org's automationSystem OverviewLOG-2644Docs
• Snapshot logs have their own category and icon and no longer create issuesSystem OverviewLOG-2916Docs
• Log, Issue and Event fields include descriptions and inline help textLogs, Issues, EventsLOG-2925Docs
• Parent logs open in a new tree viewLog ViewerLOG-2920Docs
• The Gantt chart loads large logs in chunks, adds dynamic columns, and shows CPU time in seconds and heap in MBLog ViewerLOG-2924Docs
• Logs are written faster, using less CPU per logLoggingLOG-2939Docs
• Integration logs are now categorized as Apex; their payloads display as beforeLog CategoriesLOG-2927Docs
• The Error, Warning, Debug and Event log categories are retired; severity is shown by the log LevelLog CategoriesLOG-2940Docs
• GitHub connects as a GitHub App with narrower permissions and access to private organization repositories; reconnect GitHub in Pharos to switchGitHub IntegrationLOG-2913Docs
• The MCP server builds notification rules of every type, with multiple channels and filtersMCP ServerLOG-2897Docs