troubleshoot a failed job
Diagnose authentication, submission, execution and download failures.
For: Rust developers diagnosing a Sorus job
Find the cause of an unsuccessful Sorus command or missing result, then recover without losing the original job. Have the command, exit code and any printed job identifier or submission key available. Use the symptom below to choose the relevant checks.
authentication failure
Run cargo sorus whoami and check the endpoint and credential source. SORUS_TOKEN takes precedence over SORUS_CREDENTIAL_FILE. Your identity also needs access to the tenant and repository.
request refused
Read the refusal code and details. Check the toolchain, source limits, repository authorisation, Cargo options and supported dependencies. A request refused before execution has no compilation result.
interrupted upload
Keep the submission key and local recovery record. Resume the original command with --submission-key <key>. To run changed arguments or source, start a new submission. See source recovery.
closed terminal or lost connection
The job may still be running. Reattach with cargo sorus status <job>, or use explicit cancellation to stop it. Check its state before submitting another job.
failed build or tests
Read cargo sorus logs <job>. Compare the source, toolchain and arguments with your baseline. Check for missing services, environment assumptions and unsupported network access.
platform failure
Exit 5 means a terminal platform failure, with no verdict on the workload. Keep the job identifier and failure code. Use cargo sorus jobs retry <job> for a linked retry.
Exit 4 means no outcome was observed. Check whether the job exists and is still running before retrying.
failed artifact download
Check the artifact identifier, expiry and destination path. Artifacts expire 24 hours after original admission. Choose a new destination if the file already exists.
A failed download does not change the workload’s result. Resolve access or connection problems and retrieve the output again.
contact support
Use your agreed beta support channel. Include the job identifier, client version, Cargo command, expected result and failure message with sensitive details removed. Keep credentials and private source out of the initial message. If you do not yet have beta access, contact Sorus.