# Recency boost on meta engine excludes engines **URL:** \ **Category:** Elastic Search\ **Tags:** elastic-app-search\ **Created:** [July 12, 2023, 1:26pm UTC](https://discuss.elastic.co/t/recency-boost-on-meta-engine-excludes-engines/338229 "2023-07-12T13:26:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![CodeDan](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@CodeDan](https://discuss.elastic.co/u/CodeDan)\ **Post date:** [July 12, 2023, 1:26pm UTC](https://discuss.elastic.co/t/recency-boost-on-meta-engine-excludes-engines/338229/1 "2023-07-12T13:26:40Z")
Hi Elastic community, recency boost on meta engines excludes all engines which does not contain the property. Is this a desired behavior? This can lead to misleading search results if this behavior is not known. Elastic Version v8.8.2 was used in an Elastic Cloud deployment. ---
**Author:** ![nfeekery](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nfeekery/32/117349_2.png) [@nfeekery](https://discuss.elastic.co/u/nfeekery)\ **Post date:** [July 19, 2023, 9:46am UTC](https://discuss.elastic.co/t/recency-boost-on-meta-engine-excludes-engines/338229/2 "2023-07-19T09:46:08Z")
Hi CodeDan, this is indeed a bug and not the desired behaviour. There is a workaround, however. If you index a dummy document with a valid value for the boosted field into every source engine, then the recency boost on the meta engine will no longer exclude any source engines. You can delete the dummy file afterwards as well. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 16, 2023, 9:47am UTC](https://discuss.elastic.co/t/recency-boost-on-meta-engine-excludes-engines/338229/3 "2023-08-16T09:47:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.