#TrailblazerCommunity196 debatiendo

Hi @Scott Holmes -  Create a Scheduled-Triggered Flow that runs once a day.

 Get Task records where: 

• IsClosed = False
• ActivityDate < TODAY()

 Use the Custom Notification action.  

 Send the notification to the Task Owner.  

 The notification will appear in the Salesforce notification bell.  

 If you also want the 7-day and 2-day reminders, those can remain as scheduled paths in your existing record-triggered flow. 

Hi @Olta Shehu

Welcome to the community! You can learn new skills, connect with fellow sales professionals, share ideas, and grow your career along the way. Check out this page -

1. Sales Leader
2. Sales Operations

Hi Venkat, 

Good discussion topic. Rather than picking one winner, here's what the data and Salesforce's own market direction actually show: 

Data 360 is the real foundation, not just another skill on the list. 

Salesforce's own Q3 FY26 earnings confirm Agentforce and Data 360 combined are now their fastest-growing revenue line, up 114% YoY to ~$1.4B ARR, with Data 360 ingesting 32 trillion records in a single quarter (up 119% YoY). More tellingly, Salesforce has architecturally folded Data Cloud into Data 360 as the mandatory data layer underneath Agentforce, agents are only as reliable as the data grounding them. This isn't marketing framing, it's a structural dependency: you cannot build a production-grade agent without clean, governed, unified data underneath it. 

Reference:

Agentforce is the visible layer, Data 360 is the plumbing. 

Most professionals will interact with Agentforce (the builder, agent scripting, orchestration), but the differentiated, harder-to-replicate skill will be Data 360 architecture: semantic data modeling, identity resolution, and governance. Agentforce adoption without solid Data 360 underneath is exactly what's producing "agent quietly creates cleanup work" failures being reported across 2026 implementations. 

Apex/LWC isn't going away, but its role is shifting. 

Programmatic skills remain essential for custom actions, complex orchestration logic, and Apex-invoked Agentforce actions, but they're becoming a supporting skill for AI workflows rather than the primary interface, less "build the whole feature in code," more "build the specific action an agent invokes." 

Integration is quietly becoming inseparable from Data 360. 

With Salesforce's Informatica acquisition now folded into Data 360 (bringing data catalog, MDM, and governance natively), integration skill is merging into the Data 360 skillset rather than remaining a separate specialty. If you're building integration expertise, doing it through a Data 360/MuleSoft lens rather than pure point-to-point API work is the more future-proof framing. 

My honest read: if you can only deepen one area over the next 2-3 years, Data 360 (data modeling, governance, identity resolution) has the strongest structural case, it's the layer every other skill (Agentforce, Apex actions, integrations) increasingly depends on to actually work reliably in production, not just in a demo. 

Hi @Reno Redaja

Based on Salesforce’s current Flex Credits model, Document Processing should be evaluated as part of the metered Agentforce usage rather than assuming it has a completely separate credit pool. Salesforce uses Flex Credits for metered Agentforce actions, and usage can be monitored through Setup → Digital Wallet. 

If you don’t see a specific “Document Processing” entry, check the relevant usage type/action details in Digital Wallet, since Salesforce groups consumption by usage type rather than necessarily displaying every feature as a separate line item. 

I’d also recommend checking your org’s Flex Credits Rate Card/contract, because the actual multiplier and billing treatment can depend on the specific usage type and entitlement.  

Hope this helps clarify where to look. 

Hi Garvit,

Since this is a production 3-node HA environment, I would avoid making any further changes or restarting services without first checking the Tableau Server status and logs for the affected node.

Could you please share the exact error/status shown for the Backgrounder, VizQL, Application Server, and Data Server services on node 2, along with any relevant errors from the Tableau Server logs?

If the services continue to remain in a degraded/error state after the standard checks, I recommend opening a case with Salesforce/Tableau Support so they can review the server logs and advise on the safest recovery approach without impacting the production environment.

Hope this helps.