Inspecting Computation Errors
The following are computation errors that may appear in a user’s capsule and require involvement from a Code Ocean admin. To simplify troubleshooting for both admins and the support team, each line in the table includes an explanation of how to inspect the error and outlines common root causes.
Dedicated Machine Not Allowed
For Release Capsules: The dedicated machine set for this Release Version has been disabled. Please contact your Admin for assistance.
For Non-Release Capsules: The selected dedicated machine for this run has been disabled. Please select an alternative type or contact your Admin for assistance.
Navigate to the Dedicated Machine section in the Admin panel and verify that the machine type is marked as Active.
The instance type have been recently disabled manually by an admin.
Dedicated Machine Startup Failed
The selected dedicated machine for this run failed to start. Please try again or contact your admin.
Reach out to Code Ocean support with the log bundle for resolution.
A general issue with the dedicated machine.
Computing Machine Initialization Failed
There was an internal error while preparing a new machine to perform your run. Please try again or contact your admin.
Through the AWS Console, monitor the activity log of the worker Auto Scaling group to identify the root cause.
EC2 quota for the instance type specified for flex machines may have been exceeded.
Downloading Pipeline Cache Failed
Failed to download the Nextflow cache of the pipeline run being resumed. Please try again or contact your admin.
Check the computation log for any related errors.
S3 access issues to the Results bucket.
Loading Starter Environment Failed
Selected starter environment cannot be found in the system. Try again by selecting a newer version of the starter environment or contact your admin.
Navigate to the Starter Environments section in the Admin panel and check the status of the starter environment.
Starter environment deprecated, deleted or deployment failed.
AWS Role Not Accessible
You do not have access to the selected AWS role. Please contact your admin.
Check the user’s record and the groups they belong to in your IdP.
AWS IAM role removed from one of the user/groups’ lists or user is not a member of the granted group anymore.
Error Assuming AWS Role
The system was unable to use the selected AWS role. Please contact your admin.
Fetch the related AWS IAM role from the error in the computation log and check CO’s permissions to assume this AWS role.
Misconfiguration of CO’s permissions.
Last updated
Was this helpful?