Blueprint linked to Group not pushing to existing devices: manually reassign or re-add device to trigger convergence

Android

When you link a Blueprint to a Group in the Esper Console, the configuration applies to devices that join the Group after the Blueprint is attached. However, devices that were already members of the Group before the Blueprint was linked won't automatically receive the new configuration. This article explains why this happens and how to resolve it.

Understanding Blueprint assignment timing

Blueprints are assigned to Groups prospectively—meaning the assignment only affects devices that are provisioned into the Group or moved into the Group after the Blueprint link is established. Devices that were already Group members before the Blueprint was linked don't automatically converge to the new configuration. This is expected platform behavior.

Before you begin

Verify the following before applying a resolution:

• The device is online (shows a green status in the Esper Console). Blueprint convergence requires an active connection. If the device is offline, commands will queue and execute when connectivity is restored.
• No device-level Blueprint override is in place. Device-level Blueprint assignments take priority over Group-level assignments.
• You have permission to assign Blueprints to devices or manage Group membership.

Option A: Assign the Blueprint directly to the device (recommended)

This is the fastest method and avoids Group membership side effects.

1. Open the Esper Console and go to Devices & Groups.
2. Click on the affected device to open its detail view.
3. Navigate to the Blueprint tab.
4. Select the desired Blueprint from the dropdown.
5. Click Apply.
6. Wait for the Blueprint status to update on the device detail page. Convergence activity should begin automatically.
7. Verify on the device that the target configuration (wallpaper, managed apps, restrictions, and so on) is now applied.

Option B: Re-trigger Group-based assignment by moving the device

Use this method if direct device assignment is restricted by policy or if you need to troubleshoot Group-level inheritance behavior.

1. Open the Esper Console and go to Devices & Groups.
2. Move the affected device out of its current Group into a neutral or root Group.
3. Move the device back into the original Group that has the Blueprint linked.
4. Once the device re-enters the Group, open its detail view and check whether convergence begins automatically. If not, navigate to the device detail page and click Converge.
5. Wait for convergence to complete.
6. Verify that the correct Blueprint name now appears on the device's Blueprint tab and that the target configuration is applied.

Troubleshooting convergence issues

If the Blueprint still doesn't apply after following the steps above:

• Confirm device connectivity: Check that the device shows as online (green status) in the Esper Console. If offline, wait for the device to reconnect.
• Check for device-level overrides: Navigate to Devices & Groups → Device Details → Blueprint tab and verify no conflicting device-level Blueprint assignment exists.
• Collect device logs: If convergence is initiated but the device doesn't apply the Blueprint settings, connect via ADB and run:

  adb shell logcat -d > dpc_logs.txt

  Filter the logs for Esper Agent and Blueprint tags. Save these logs for support.
• Check Blueprint consistency: If convergence fails across multiple devices even after direct assignment, note your Enterprise name, device serial numbers, Blueprint ID, and Group ID for support.

Still need help?

If you've tried both options and the Blueprint still isn't applying to your devices, contact Esper Support. Include your Enterprise name, affected device serial numbers, Blueprint ID, and Group ID to help us investigate quickly.