How do you troubleshoot a Flink job that fails to start from StreamPark Console?

StreamPark centralizes the diagnostics you'd otherwise gather from several places, so troubleshooting a startup failure usually follows the same short path.

1. Check the start log — in the job's row in the application list, an eye-shaped icon opens the submitted job's start logs, showing exactly what StreamPark sent to the cluster and any submission-time error.
2. Check the build log — if the job uses Upload Jar via Project Management, confirm the most recent build actually succeeded; a stale or failed build is a common false alarm that looks like a startup issue.
3. Check cluster-side resources — for YARN, confirm the configured queue exists and has capacity; for Kubernetes, confirm the namespace, service account, and RBAC are set up correctly.
4. Check job configuration — execution mode, Flink version, and any Flink SQL connector dependencies are the most common source of a mismatch between what the job expects and what's actually available.

Because these signals live in one console, you rarely need to jump out to a separate YARN or Kubernetes dashboard just to find the first error.