Compute rejected your input
If Compute rejects your input, how to find the cause, fix it on your side, and check the first request did not go through.
Identify which input was rejected
Your client reports invalid data, an unsupported format, or a policy refusal. Start with the safe error code and the field or stage named by the response. Do not upload the whole file again just to obtain a clearer error.
A metadata request and its referenced artifact have different limits. The REST JSON limit is not the maximum file size. A file extension does not prove that its bytes match the required format.
Correct the actual problem
Wrong fields or format: compare the input with the selected operation's current schema. Fix unsupported fields, missing values, or the actual encoding locally. Do not rename a file to evade a check.
Too large: identify whether the refusal concerns metadata, an artifact, or the operation's content limit. Use the supported preparation path rather than truncating required evidence or inventing manual execution partitions.
Credential detected: stop. Remove the credential from the task and use the integration's protected setup. Treat a credential already disclosed outside its intended boundary as a possible exposure.
Data or jurisdiction refused: review data profiles. Do not relabel restricted data as public or synthetic. Customer approval does not override an unsupported category.
Preserve existing work
A rejected request does not erase an earlier upload or tell you whether a previous job was admitted. Keep its reference and inspect current state separately.
A corrected input is changed work. Review the matching snapshot, quote and approval before submitting it as new work. Do not reuse an old approval for different bytes.
Confirm or stop
Success is a valid input that meets the selected operation and policy, followed by the appropriate review. Stop when classification, format, or prior submission remains unclear.
Use Contact Lithi with the data category, format, approximate size, safe error code, and reference when available. Do not include credentials, private messages, signed URLs, or full customer files.