Deployments are continuous. When you create a deployment, AWS IoT Greengrass rolls out the deployment to target devices that are online. If a target device isn't online, then it receives the deployment the next time it connects to AWS IoT Greengrass. When you add a core device to a target thing group, AWS IoT Greengrass sends the device the latest deployment for that thing group.
Are you observing different behaviour?
How to remove a component from running on an installationAccepted Answerasked 3 months ago
Greengrass - best way to handle setting a topic based on the core device?Accepted Answerasked 3 months ago
Pre loaded Device component with Greengrass installerasked 5 months ago
How to connect an IoT Thing to Greengrass V2asked 2 years ago
Is there a way to read the group name in a component or environment var?asked 2 years ago
[greengrass]deploy the component from thing group to thingasked 3 months ago
IoT thing shadow and Greengrass componentasked 2 years ago
How to retreive GreengrassV2 Core Device's AWS IoT Thing nameAccepted Answerasked 2 years ago
Unable to deploy custom component to core deviceAccepted Answerasked a year ago
Unable to deploy Greengrass V2 available componentasked a day ago