Play Store app installation via Blueprint fails account-wide

Android

When Play Store apps assigned through a Blueprint fail to install across every device on your account, no apps from the managed Google Play Store are delivered after provisioning or Blueprint application.

Why this happens

Blueprints rely on a valid Enterprise Enrollment Manager binding between your Esper account and a managed Google Play account. If the wrong Google account is bound — or the binding has lapsed — Esper cannot communicate with Google Play to push app installations. Separately, if a previous Blueprint operation is still queued or in progress on a device, new operations will not execute until the queue clears.

Steps

1. Verify your managed Google Play binding. In the Esper Console, go to Enterprise Settings → Google Services. Confirm that the Google account listed as your Enterprise Enrollment Manager is the correct business account. If the wrong account is shown, the binding must be removed and re-established with the correct account before any Play Store apps can be delivered. Contact Esper Support to safely re-bind your account without losing existing device enrollments.
2. Check for stuck or queued operations on affected devices. Go to Devices & Groups → [Device Name] → Activity Feed. Look for any operations in a Queued or In Progress state. New Blueprint operations will not execute on a device that is already processing — or waiting to process — a prior command. Wait for all pending operations to reach a terminal state (success or failure) before continuing. If an operation appears stuck, allow it to time out naturally rather than issuing a new command on top of it.
3. Confirm the Play Store app is correctly configured in the Blueprint. Go to Blueprints → [Blueprint Name] and open the Apps & Configuration section. Verify that the intended Play Store app is listed and set to install. If it is missing, add it, save the Blueprint, and publish the change before re-applying.
4. Re-apply the Blueprint to a test device. Go to Blueprints → [Blueprint Name] → Apply and select a single affected device to test. Applying to one device first limits impact if the root cause has not yet been fully resolved.
5. Monitor the Activity Feed for convergence status. Go to Devices & Groups → [Device Name] → Activity Feed and watch for the Blueprint operation to move through In Progress to Success. This confirms that Esper and the device have fully synchronized.

Verify: Go to Devices & Groups → [Device Name] → Apps. The Play Store app should appear with a status of Installed within 10 minutes of a successful Blueprint convergence. The Activity Feed entry for the operation should show Success.

If this doesn't resolve it

If Play Store app installations are still failing after confirming the Google Play binding and clearing queued operations, contact Esper Support and include the following:

• Your enterprise tenant name
• The Google account currently bound as your Enterprise Enrollment Manager (visible in Enterprise Settings → Google Services)
• The Google account you intended to bind
• The name of the Blueprint being applied and the app(s) failing to install
• A screenshot or export of the Activity Feed from at least one affected device showing the failed operation
• Confirmation of whether affected devices are showing as Online in Devices & Groups

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.