TL;DR: If two projects both have a service called my-service, the by-name lookup errors and asks you to pass project_id or cloud_id, it never guesses for you. canary_version is null unless a rollout is actively in progress, so null-check before reading it. [Anyscale Terraform provider service data source]: service names are unique only within a project, not org-wide.

## Fix
1. If two projects both have a service called my-service, the by-name lookup errors and asks you to pass project_id or cloud_id, it never guesses for you. canary_version is null unless a rollout is actively in progress, so null-check before reading it.
   Expected: this specific failure stops.
2. If two projects each have a service called my-service, the by-name lookup errors out asking you to set project_id or cloud_id to disambiguate; it never silently guesses. canary_version is null except while a rollout is actively in progress, so check for null before reading fields off it. error_message carries the error from the most recent API request against the service, null otherwise.
   Expected: this specific failure stops.

## Details
[Anyscale Terraform provider service data source]: service names are unique only within a project, not org-wide. And error_message holds the latest API error against the service, null when things are fine. Context: Anyscale Terraform provider service data source: service names are unique only within a project, not organization-wide.

## When to use
You hit exactly this: Anyscale Terraform: service names unique per project only, null-check canary_version (service_lookup) in Anyscale Terraform.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Anyscale Terraform.