AWS Greengrass IOT Job ID does not exist

When you encounter AWS IoT Greengrass deployments that are "stuck" in an IN_PROGRESS state and find that the associated IoT job ID no longer exists, there are a few potential explanations.

AWS IoT jobs can indeed be removed or become unavailable after a certain period. If you're trying to check a deployment that was created almost a week ago, it's possible that the job information is no longer available in the system.

To check the deployment status for a Greengrass core device, you should follow these steps:

1. First, retrieve the deployment ID using:

aws greengrassv2 list-deployments --target-arn <targetArn>

2. Then get the deployment details including the IoT job ID:

aws greengrassv2 get-deployment --deployment-id <deploymentId>

3. Finally, check the job execution status:

aws iot describe-job-execution --job-id <iotJobId> --thing-name <coreDeviceThingName>

If the job ID doesn't exist when you run the describe-job-execution command, it could be because:

1. The job was canceled when a newer deployment was created (when a new deployment revision is created, the status of the previous revision's AWS IoT job changes to "CANCELLED")
2. The job information has been purged from the system after a retention period
3. There might be connectivity issues between your core device and AWS IoT Core

For devices that appear stuck in an IN_PROGRESS state, check that:

• The core device has internet connectivity
• The device can reach the AWS IoT data endpoint
• Review the Greengrass logs for errors that might reveal root causes

You might need to create a new deployment to resolve the issue for devices that are stuck in an indeterminate state.
Sources
Check deployment status - AWS IoT Greengrass
Troubleshooting AWS IoT Greengrass V2 - AWS IoT Greengrass

Hi what region are you experiencing this issue in?

Do you have logs from the affected devices?

Is this a deployment to a thing or a deployment to a thing group? If it is a thing group deployment, make sure that the thing is part of the thing group. Per the first response, obtain the deployment ID and call get-deployment to find the Job ID. Once you have the Job ID, you'll be able check executions of that job with list-job-executions-for-job.