Hello Cloud Connector enthusiasts!

If you’ve ever stared at a stubborn connectivity issue wondering “Why won’t this tunnel connect?” or “What’s blocking my RFC calls?”, you’re in good company. The Cloud Connector has a powerful, often underutilized feature right in the admin UI: the Troubleshooting page under Connector > Troubleshooting. This isn’t just a log viewer—it’s an intelligent diagnostics framework that detects, analyzes, and even suggests fixes for common issues. Here’s how it works, what it covers, and how to make it part of your daily routine.

What is the Troubleshooting Framework?

Certain types of issues—think tunnel timeouts, email alerts failing, or backend connection hiccups—are automatically detected and processed by the framework. They appear as diagnoses in a handy table on the Troubleshooting screen. Each diagnosis summarizes the problem and provides likely causes and suggested fixes to help you act fast.

Important note: These causes and fixes are hints, not guaranteed solutions. Always verify in your environment.

Key details in each diagnosis

Open any entry to drill into the details. For recurring issues, the framework won’t spam your table—it increments an occurrence counter instead. In the details pop-up (Actions column), you’ll see:

• Creation Date: When the issue was first recorded.
• Removal Date Unless Recurring Earlier: Many diagnoses auto-delete 24 hours after the last occurrence. No repeat? Poof—gone!
• Minimal, Maximal, and Average Recurrence Interval: Shown for issues occurring multiple times within 24 hours—great for spotting patterns (e.g., “every 5–10 minutes”).
• Technical Exception: Type and message (for example, io.netty.channel.ConnectTimeoutException).

You can delete diagnoses manually, but if the issue recurs, it’ll reappear with the counter reset to 1.

Alerting integration: Stay notified without the noise.

Background issues (like failing incoming requests) can generate alerts, which—depending on Alerting > E-Mail Configuration—may trigger automatic emails.

• New diagnoses alert once; recurrences don’t spam your inbox.
• Want to skip emails for new troubleshooting diagnoses? Uncheck “Troubleshooting” under Observation Configuration.
• Deleting a diagnosis doesn’t clear the related alert—remove that manually if needed.
• Since auto-recovery isn’t always detectable, some diagnoses and alerts can linger until the 24-hour timeout or manual cleanup.

What’s already covered? A look under the hood

The framework already detects and diagnoses several high-impact scenarios:

Tunnel problems

• Connection timeout (io.netty.channel.ConnectTimeoutException): The Cloud Connector can’t establish in time the tunnel to the SAP Connectivity Proxy either in your BTP or in the SAP Solution which deployed the Connectivity Proxy. Find more information in the documentation. Typical causes include firewall rules, proxy misconfiguration, or network latency.

Alert email failures

• Sender address rejected (“You are not authorized to send as…”): Check that the configured sender matches an authorized account on your mail server.
• SMTP connection failure (“Could not connect to SMTP host: …”): Verify host, port, credentials, and whether your network/firewall allows outbound SMTP traffic.

RFC requests

• Incomplete or erroneous Access Control configuration: RFC calls fail when the target Function Module isn’t allowed in Access Control or the ABAP backend connection is misconfigured. A classic “works in browser, fails in RFC” situation—double-check your Access Control entries.

Internal host connection tests

When you run a connection test to an internal (on-premises) host, you might see:

• Host unknown: DNS can’t resolve the configured hostname.
• Service or logical port unknown: The specified port/service isn’t reachable or recognized.
• Backend unreachable / Connection refused / Timeout: The target system isn’t responding as expected.
• Certificate not accepted: TLS/SSL handshake fails because the backend’s certificate isn’t trusted by the Cloud Connector.

How to use it in your daily workflow

1. Navigate: Cloud Connector UI > Connector > Troubleshooting.
2. Scan the table: Sort by recency or occurrences. Prioritize high counters.
3. Drill down: Open entries to review causes and suggested fixes. Apply changes (e.g., revalidate access controls, adjust firewall rules).
4. Monitor alerts: Pair with email settings for proactive notifications.
5. Clean up: Delete resolved entries and watch for recurrences.
6. Escalate smartly: Capture exception screenshots and collect logs before opening an SAP Support ticket.

When it doesn’t cover your issue

The framework focuses on common, auto-detectable configurations. For deeper analysis:

• Check the Trace tabs (e.g., Tunnel, RFC) for detailed request/response data.
• Review Account > Connectivity Tests for subaccount health.
• Consult the SAP Help Portal: Cloud Connector Troubleshooting for comprehensive guidance.

The Troubleshooting page is a quiet time-saver. Before diving into traces or opening a ticket, spend 30 seconds in Connector > Troubleshooting. There’s a good chance the framework already flagged the issue and has a hint ready for you. Better yet, it’s passive—no agents or extra setup. It’s always on and keeps getting smarter as new issue types are added over time.

Have you uncovered a gem with the Troubleshooting framework? Share your experience in the comments!

Stay connected,
Your Cloud Connector Team