This usually happens if Elasticsearch is out of date with latest case changes on your environment.
Is this an issue that is happening on your local CommCareHQ instance or Dimagi's www.commcarehq.org?
If this is happening on your instance, you need to make sure that the Pillowtop service is fully caught up using the pillowtop section in https://YOUR_HQ/hq/admin/system/. If that is not caught up or stuck, you need to troubleshoot pillowtop service to make it run correctly. Please see relevant documentation at Firefighting Guide — CommCareHQ Deployment documentation