Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.galileo.ai/llms.txt

Use this file to discover all available pages before exploring further.

This page covers the most common errors users hit and what to do about them. If you’re stuck on something not listed here, reach out via the Galileo support channels.

Account

Can’t sign in

You see Invalid email or password on the sign-in page.
Likely causeWhat to try
Wrong passwordClick Forgot your password? on the sign-in page to reset it.
Account doesn’t existClick Create account to create an account.
Typo in the emailRe-check the email — case matters in some setups.
If you reset your password but still can’t sign in, the reset email may not have arrived. Check spam, and confirm the email matches your Luna Studio account.

Integrations

Save changes button is disabled

The modal won’t let you submit.
Likely causeFix
A required field is emptyFill in every field marked required.
JSON in a code-editor field doesn’t parseThe editor highlights the offending line. Common: trailing comma, smart quote.
Disclaimer switch isn’t toggled onSome providers gate save behind the “I acknowledge…” switch.

Provider returns 401 / unauthorized

Validation passes when adding the integration but runs fail with provider auth errors.
Likely causeFix
Stale API keyUpdate the integration with a fresh key.
Wrong region (Azure / AWS)Confirm the resource is in the region you specified.
Insufficient quotaCheck your provider’s quota dashboard. Some providers return 429 instead of 401.

Vertex AI: GCS uploads fail

You enabled Support file uploads but uploads to your bucket fail.
Likely causeFix
Service account lacks permissionsGrant Storage Object Creator (or higher) on the bucket.
Wrong object path prefixDefaults to galileo-uploads. Make sure the prefix matches your IAM policy.
Bucket name typoBucket names are case-sensitive in some setups. Double-check.

AWS: Assumed role fails

You picked Assumed Roles but Luna Studio can’t assume the role.
Likely causeFix
Trust policy missingAdd Galileo’s account principal to the role’s trust relationship. (See AWS docs from the integration modal footer.)
External ID mismatchIf you set an external ID, confirm it matches what Luna Studio sends.
Wrong regionThe role must exist in the region you specified.

Datasets

Validation error: “Missing column”

You see Missing column "label" (or "input") after adding a dataset.
Likely causeFix
Column not in CSV/JSONLAdd the column to the file and re-add the dataset.
Column named differentlyRename to the literal input and label keys — Luna doesn’t auto-detect.
Training logs are unlabelledUse Add training logs in Step 3. Luna Studio will label the logs before training.

Validation error: “Could not fetch URL”

Luna couldn’t pull the file from the URL you gave it.
Likely causeFix
URL requires authFor s3:// use AWS integration; for gs:// use Vertex AI with file uploads on.
URL returns 404Open the URL in a browser to confirm it serves a file.
Content type unsupportedRe-host as .csv or .jsonl and use a direct link.

Generated dataset doesn’t look right

You ran Generate from test set and the samples are repetitive, off-topic, or mislabelled.
Likely causeFix
Test set seeds aren’t representativeAdd more diverse rows to the test set, then regenerate.
Generation model too smallSwitch to a larger available model from one of your configured providers.
Metric prompt is ambiguousClarify the prompt; click Regenerate with the “Provide own feedback” reason.

Runs

Run failed

Failure reasonWhat to do
Out-of-memory on base modelSwitch to Luna Small, or shrink the training set (regenerate with fewer rows).
Training failed after N epochsOften a transient compute issue. Re-launch with the same config.
Provider error (during generation)Re-check the integration that backs the generation model. Re-launch.
Validation error on linked datasetThe dataset changed since launch (Galileo source updated). Re-add and re-launch.

Register metric fails with duplicate name

The Galileo metrics store already has a metric with that name.

Stuck in Queued

If a run sits in Queued for more than a few minutes, the most likely causes are:
  • Heavy load. Luna provisions training capacity per region. Wait a few more minutes.
  • Integration removed. If the integration backing the metric template was removed after launch, the run can’t allocate. Re-add the integration and launch a new run.
If neither applies, contact Galileo support.

Where to go next

FAQ

Common questions about how Luna Studio works.

Quickstart

End-to-end walkthrough.