#Tableau27 discutindo

Hi Vikas,

Test Connection and the flow run are not the same session. Test Connection uses you. A Prep flow on Tableau Server runs with the credentials embedded on the flow, under the server account that executes flows. Other extracts can keep working while this flow doesn't, if this one is the only place those credentials aren't embedded.

The message you pasted is on the output step: unable to connect to that data source. That's the output connection, not automatically the Oracle input. A flow that writes several files has an output connection of its own, and that's the one I'd open first.

On the Oracle side, the process that actually runs the flow has to see the JDBC driver and oracle.properties. Dropping the file under flowprocessor while that process is already up doesn't always get picked up. Restart the flow services after the file is in place, then run this one flow again.

I wouldn't call this a tnsnames problem until the output step still can't connect when you run it as the same account the server uses. I also don't have a published defect for 2026.2.1 that matches this, so I won't invent one.

Hi Alex!

If the trail is under the /content/employee/ path and marked Private

, it’s likely restricted to a specific Salesforce employee audience rather than being a trail that an individual user can make publicly accessible. 

I’d check whether the trail has an internal sharing/audience setting that the trail owner or Salesforce learning administrator can modify. If your colleagues are Salesforce employees but still can’t access it, their Trailhead/employee permissions or audience eligibility may need to be checked. 

If there’s no option to change the audience from the Trailhead side, this would likely need to be handled by the Salesforce/Trailhead team rather than by the individual trail owner. 

Hi Elizabeth!

Yes, MuleSoft can help, especially if you need more than a straightforward Tableau-to-API connection. 

If Equina exposes the required data through REST APIs, you could either connect Tableau directly using its Web Data Connector, or use MuleSoft as an integration layer:

Equina REST API → MuleSoft → transformed/standardized data → Tableau

MuleSoft becomes useful when you need authentication handling, pagination, data transformation, error handling, scheduling, or combining Equina data with other systems. You could also expose a simplified API from MuleSoft for Tableau to consume.

If the reporting requirements are relatively simple, I’d first test the WDC approach. If you need recurring data loads, complex transformations, or multiple sources, MuleSoft would provide more flexibility.

@preethi philipose

That "child process suspended by another process" error is almost always your antivirus / endpoint-security (EDR) software stepping in — Tableau spins up a small helper process to read the file, and the security tool suspends it before it can finish, so it can't resume. It's not really the Power Query itself. 

Ask IT to add Tableau to the AV/EDR exclusions — the Tableau Desktop Bin folder + tableau.exe (and its child processes), plus the Tableau temp/repository folder. Quick way to confirm it's the culprit: temporarily disable the AV (or try on a machine without that EDR) and see if the error clears. 

If this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂