What could cause a 'SQL validation failed' error when executing a Flink statement in Confluent Cloud

Updated
August 19, 2025 06:36

Description

When executing a Flink statement from the Confluent Cloud UI, you may receive an error similar to:

SQL validation failed. 
Caused by: Table (or view) XXXXX does not exist, may be on a private cluster, 
or you do not have permission to access it.
If the cluster is private, please connect using a private network.

Applies To

Confluent Cloud

Flink

Cause

Permission Issue
Network connectivity
Incorrect Statement

Resolution

Make sure the Principal has the required permissions: What are the minimum rolebindings required to run a Flink query in Confluent Cloud
Make sure your host has network connectivity to the Flink endpoint: Test Connectivity to Confluent Cloud

Example:

$ export BOOTSTRAP=flink.germanywestcentral.azure.private.confluent.cloud
$ openssl s_client -connect $BOOTSTRAP:443 -servername $BOOTSTRAP -verify_hostname $BOOTSTRAP

3. If both the previous points are validated, ensure your statement is written correctly, as the same error will appear if, for example, the table or view does not exist.