#Salesforce136 discutindo

Hi Rakesh - the root issue is that the window online/offline events (and navigator.onLine) are inherently unreliable, and Linux Chrome is the worst case. Chromium marks the browser 'online' whenever there is any network interface with an IP - even a virtual or IPv6 adapter with no real internet - and it often never fires the offline event on Linux. So on that one Ubuntu user's machine the events genuinely will not fire; it is a documented Chromium limitation, not your code. 

So do not gate your OmniScript logic on those events. Two robust patterns instead: 

1. Handle the failure at the call, not before it. Wrap the DataRaptor IP remote action so that when it fails (network error or timeout) you catch it and show your friendly 'you are offline' message plus a real retry - rather than trying to predict offline up front. In OmniScript, use the element's error handling / a Set Errors plus conditional navigation so the hard error banner never shows. 

2. If you want a proactive signal, run a lightweight heartbeat - a periodic fetch to a tiny known endpoint with a short timeout - and treat a failed or timed-out fetch as offline. That actually tests reachability, which the browser events do not. 

navigator.onLine is fine as a hint (if it says false, you are definitely offline), but never as the source of truth. Catching the actual remote-action failure is what fixes the ungraceful error for everyone, including that Ubuntu user. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

@Curtis Hale and @Kundan Kumar Jha  

I had a case in for this issue. Here is the response from Salesforce Support: 

 "Based on our investigation, the current behavior appears to be working as designed following a recent product update. We confirmed that this is not related to user permissions, profiles, or configuration changes in your Salesforce org. 

The update introduced changes to the My Feed experience, including: 

The red “X” previously used to dismiss individual feed items is no longer displayed. 

The Open Count is also no longer shown. 

Users can continue to view and filter their My Feed notifications; however, the option to manually dismiss individual items is no longer available in the updated experience. 

This behavior is consistent across users and has also been observed in other Salesforce orgs following the update. Based on the information currently available, it does not appear to be an org-specific issue or product defect. 

Additional information about the related product changes is available in the Salesforce Release Notes: 

https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_sales_engagement_on_core.htm&release=262&type=5

We understand that the removal of the dismiss option affects how your users manage their daily notifications, and we appreciate you bringing this change to our attention." 

Hey Bhagyavan, 

This is an internal server error on Salesforce's own infrastructure (the message itself confirms "

support team has been notified"), not something wrong with your account setup or browser. 

Since this happened right after login on a specific home page, try: 

- Wait a few minutes and refresh, transient internal errors often clear on retry 

- Try navigating directly to Setup or a different tab (like an object list view) instead of the Home page, if that works, the issue may be specific to a component on your Home page (like a broken dashboard or custom Lightning component) 

- Clear browser cache or try incognito, rules out a stale cached page state 

- If it persists across all pages/browsers, log a case with Salesforce Support and include the Error ID: 605878076-277435 (-652286695), that ID lets their support team pull the exact server-side log for your issue 

Since the org is on a Developer Edition-style domain (

), if this is a Trailhead Playground, spinning up a fresh one may be faster than waiting on a support case. 

Reference:

Hey Rosie, 

Steve's on the right track. Adding the concrete steps to build on that: 

1. Create a Record-Triggered Flow on Opportunity, trigger it "A record is created," run Before the record is saved (this lets you set the field without a separate DML/save cycle) 

2. Add entry criteria for your specific Opportunity Type, so it only fires for that record type 

3. Add a Get Records element to query your "2024 Sponsorship Amount" custom object, filtered where the Account field equals $Record.AccountId 

4. Add an Assignment (or just set it directly if using the auto-layout field-update path) to set your Opportunity's amount field to the value pulled from that Get Records result 

This requires a Lookup or Master-Detail relationship between your custom object and Account (not Opportunity directly), since you're querying the custom object by Account, then writing the result onto the new Opportunity. Before-save flows are the standard, most efficient way to auto-populate a field at creation without an extra save cycle. 

Reference:

Hi @Vasu Kasula

Did you try below options- 

1. Refresh the Decision Table Used for List Price 

2. Verify the Product Discovery Pricing Procedure and Context Definition 

3. Rebuild the Product Discovery Search Index 

Hi @Rhythm Sharma,

This might be part of Free Data Cloud Account and you would get 2 Tableau Creator licenses.

Reference: 

https://help.salesforce.com/s/articleView?id=000396380&type=1

You would need to reach out to you Account Executive regarding salesforce licenses.

Thanks!