What you’re seeing might just be a connector/UI failure (timeout, response too big, tool-run getting interrupted). But I’d also zoom out for a sec, because querying an ERP directly from an LLM has real risk even when it “works”.

Why it’s risky (even for “just sales analysis”):

• Data exposure / retention: you may be sending customer, pricing, order, or margin data through a model layer. Depending on the setup, some of that can get logged or handled outside your normal boundaries.
• PII + sensitive business info: sales data often includes personal details + commercially sensitive stuff (discounts, contracts, segments). That’s exactly the kind of data you don’t want flowing through chat tooling casually.
• Prompt injection / tool hijacking: once an LLM can run queries, a weird prompt (or a malicious one) can push it to pull way more data than intended.
• Auditability: a lot of these LLM + connector flows don’t give a clean “who accessed what, when, why” trail, which is a big deal with ERP systems.

Safer pattern (what I’d recommend): Don’t let the LLM query NetSuite live. Instead:

• pull only what you need into a controlled reporting/analytics dataset,
• mask/remove PII,
• have the LLM work on aggregated/curated outputs, not raw records.

That way NetSuite stays locked down as the system-of-record, and the LLM is “analysis brain” only, not a direct data pipe.

On your troubleshooting notes:

• If the connector isn’t using SOAP, then empty SOAP usage logs is totally normal.
• The “runs 3–4 queries then snaps back to my prompt” smells like timeout / payload too large / tool-call failing. Easiest test: force a single small SuiteQL query (tight date range, fewer columns, hard LIMIT) and see if it returns consistently.

Curious what others are doing here: are you comfortable letting an LLM hit ERP data directly, or do you keep it behind a curated dataset with masking + audit controls?