Understanding the status of your Code Engine fleet

After a fleet is created in Code Engine, you can check the status of the overall fleet, as well as the statuses of any tasks. You can use this information to help with debugging.

Fleet status

The fleet status indicates the overall operational status of a fleet. It is not related to the statuses of tasks. To find out which tasks completed successfully, check the task statuses.

Fleet statuses
Fleet status	Description	Possible user actions
Pending	There are tasks pending, but no tasks running.	Add tasks, Cancel, Delete
Running	There are running tasks.	Add tasks, Cancel, Delete
Standby	All tasks have been completed, there are no pending tasks. The fleet is waiting for new tasks to be added. Whether worker nodes are provisioned depends on the fleet's scaling parameters.	Add tasks, Cancel, Delete
Canceling	A cancellation is in progress. Some instances are still running. Running tasks either complete or are terminated, depending on the cancellation mode. Pending tasks are canceled and do not run.	Delete
Canceled	The cancellation is complete. All pending and running tasks were canceled. All workers have been deleted. The fleet still counts toward the project quotas.	Delete
Deleting	Deletion is in progress. Running tasks are terminated. Worker nodes are deleted or being deleted. The fleet is removed when deletion completes.	None

Checking fleet status in the Code Engine console

Locate the Code Engine Projects page.
Click the name of your project to open the Overview page.
Click Fleets to open a list of the fleets defined in your project.
The status of each fleet appears in the Status column of the table.

Checking fleet status in the Code Engine CLI

To check the status of your fleet, run the ibmcloud ce fleet get command. Specify the fleet ID.

Example

ibmcloud ce fleet get --fleet-id 1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e

Example output

Getting fleet '1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e'...
OK

Name:            fleet-0123456789  
ID:              1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e  
Status:          running  
Created:         2025-09-26T10:46:02Z  
Project region:  eu-de  
Project name:    myproj  

Tasks status:             
  Pending:     893  
  Running:     12  
  Failed:      0  
  Canceled:    0  
  Successful:  96  
  Total:       1001  

Code:                     
  Container image reference:  icr.io/codeengine/helloworld  

Tasks specification:      
  Task state store:  mytaskstore  
  Indexes:           0-1000  

Resources and scaling:    
  Container instance resources:    
    CPU per instance:     1  
    Memory per instance:  2G  

  Scaling settings:                
    Maximum container slots:  12  
    Minimum container slots:  0  
    Spare container slots:    0  
    Scale-down delay:         0s  

  Resiliency settings:             
    Maximum retries per task:  3  

Network placement:        
  Subnet pools:    
    Name:                my-pool
    Number of subnets:   1  
                         
    Subnet CRN:          crn:v1:bluemix:public:is:eu-de-1:a/abcdefabcdefabcdefabcd1234567890::subnet:1a1a-2b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f   
    Security Group CRN:  crn:v1:bluemix:public:is:eu-de:a/abcdefabcdefabcdefabcd1234567890::security-group:2b2b-3c3c3c3c-4d4d-5e5e-6f6f-7g7g7g7g7g7g  

Environment Variables:    
  Type     Name   Value  
  Literal  FOO    bar

Task status

The task status indicates the health of individual tasks running on the fleet. Each task runs on a single instance.

Description of task statuses
Task status	Description
Pending	The task has no associated instance.
Running	The task has exactly one associated instance running.
Succeeded	The last instance started on behalf of this task ended successfully and the task is no longer running.
Failed	The last instance started on behalf of this task failed and the task has reached its maximum number of retries. The task is no longer running. Failed tasks return to the Pending status until the maximum number of retries has been met.
Canceled	A user has canceled the fleet and the task is no longer running. This task was canceled before it succeeded or failed.

Checking the status of tasks in the Code Engine console

Open your fleet page:
1. Locate the Code Engine Projects page.
2. Click the name of your project to open the Overview page.
3. In Fleets, click the name of your fleet.
The status of each task appears in the Status column of the table.

Checking the status of tasks in the Code Engine CLI

To check the status of your tasks, run the ibmcloud ce fleet task list command. Specify the fleet ID.

Example

ibmcloud ce fleet task list --fleet-id 1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e

Example output

Listing serverless fleet tasks...
OK

Task index  ID                                    Batch name  Status     Result code  Started               Duration  Worker name  
0           5b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  default     succeeded  exit_0       2026-08-06T19:48:13Z  26s       fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-0 
1           4b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  default     running                 2026-08-06T19:52:14Z            fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-1 
2           3b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  test2       pending
3           2b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  test2       running                 2026-08-06T19:57:14Z            fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-1 
4           1b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  test2       failed     exit_0       2026-08-06T19:58:14Z  0s        fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-0 
foobar      0b0b0b0b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  test3       succeeded  exit_0       2026-08-06T19:59:14Z  1m        fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-2

Worker node status

You can check the status of the worker nodes that your instances run on.

Checking the worker node status of a fleet in the Code Engine console

Open your fleet page:
1. Locate the Code Engine Projects page.
2. Click the name of your project to open the Overview page.
3. In Fleets, click the name of your fleet.
Click the Workers tab.
The status of each worker appears in the Status column of the table.

Checking the worker node status of a fleet in the Code Engine CLI

To check the status of the worker nodes of a fleet, run the ibmcloud ce fleet worker list command. Specify the fleet ID. For a complete list of command options, see the CLI reference.

The statuses of the workers appear in the Status column.

Example

ibmcloud ce fleet worker list --fleet-id 1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e

Example output

Listing serverless fleet workers...
OK

Name                                          ID                                    Status        Profile   IP           Zone     Version  
fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-0  2b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  running       cx2-2x4   10.242.0.42  eu-de-1  v1.0.15
fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-1  3c3c3c3c-4d4d-5e5e-6f6f-7g7g7g7g7g7g  initializing  cx2-8x16  10.242.0.43  eu-de-1  v1.0.15

To check the status of a single worker node, run the ibmcloud ce fleet worker get command. Specify the fleet ID and the worker name. For a complete list of command options, see the CLI reference.

Example

ibmcloud ce fleet worker get --fleet-id 1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e --worker-name fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-42

Example output

Getting serverless fleet worker...
OK

Name:          fleet-1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e-42  
ID:            2b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  
Created:       2025-09-26T20:05:33Z  
Status:        running  
Version:       v1.0.15  
Fleet ID:      1a1a1a1a-2b2b-3c3c-4d4d-5e5e5e5e5e5e  
Project name:  myproj  
Project ID:    3c3c3c3c-4d4d-5e5e-6f6f-7g7g7g7g7g7g  

Network placement:      
  IP address:    10.242.0.42  
  Network zone:  eu-de-1  
  Subnet CRN:    crn:v1:bluemix:public:is:eu-de-1:a/abcdefabcdefabcdefabcd1234567890::subnet:1a1a-2b2b2b2b-3c3c-4d4d-5e5e-6f6f6f6f6f6f  

Profile information:    
  Profile:       cx2-2x4  
  vCPUs:         2  
  Memory (GiB):  4