Performance Optimization for articlesByLocation Query
Release
Author:
Samith Jayawardana
Changed on:
19 Feb 2026
| Target release date: | 2026-02-19 |
|---|---|
| Release status: | Planned |
Description
This release introduces performance enhancements for the`articlesByLocation` GraphQL query by applying an optimized query strategy that improves response times for the most common search patterns.These performance improvements benefit all queries, including those that already specify explicit date ranges.Changelog
With these optimizations aimed at improving efficiency and reducing response times, a date range resolution logic has been introduced for the article's`createdOn` field. This logic ensures that queries target a manageable timeframe, as performance can degrade when articles from an extensive history are included in every query. Feature Activation
To ensure that any impact from date range enforcement can be managed, this feature is disabled by default for existing accounts. It can enabled through the`fc.graphql.compatibility.articlesByLocation.queryStrategy` feature flag setting with the following values:`static`: feature is disabled (default for existing accounts)`dynamic`: the system applies an optimized query strategy to`articlesByLocation`, resulting in improved response times. Furthermore, the system applies two behaviors to the`articlesByLocation`GraphQL query:- Automatic date range resolution: If a query omits the
`createdOn``from`and/or`to`parameters, the system automatically calculates and applies them based on a configurable default period (default: 30 days). - Maximum range enforcement: If a query specifies a
`createdOn`range that exceeds the configured maximum, the range is automatically truncated.
For full technical details on how date ranges are calculated, see the setting documentation.
- Automatic date range resolution: If a query omits the
Adjusting the Defaults
If the 30-day default doesn't suit your requirements, both the default and maximum period are configurable at the account level before you enable the feature. For more details see the individual documentation pages.| Released capability depth: | Enhancement |
|---|---|
| Release bundle / Capability type: | Platform |
