fc.graphql.compatibility.articlesByLocation.maxSearchPeriodDays
Setting
Changed on:
18 Feb 2026
| Setting Area | System |
|---|---|
| Supported context levels: | ACCOUNT |
Overview
This setting acts as a safety limit to prevent queries from scanning too much data at once. When you specify both`from` and `to` dates in an `articlesByLocation` query, this setting enforces a maximum time span between them. If your date range exceeds this limit, the system automatically truncates it to stay within the maximum.When this applies:- Only when
`fc.graphql.compatibility.articlesByLocation.queryStrategy`is set to`dynamic` - Default for new accounts created on or after 2026-02-16
- Opt-in for existing accounts
- Only enforced when BOTH
`from`and`to`dates are explicitly provided
Values
| Data Type | Values |
|---|---|
| INTEGER | Default Value:
|
Detailed technical description
This setting enforces a maximum time span between`from` and `to` dates in the `createdOn` filter. When both dates are explicitly provided and the interval exceeds this limit, the system automatically truncates the range.How It WorksIf both
`from` and `to` are provided and the interval exceeds `maxSearchPeriodDays`:`from = remains unchanged (as requested by user)``to = from + maxSearchPeriodDays (recalculated)`
Example:
If set to 30 days (default) and you query for 5 months of data (Jan 1 to May 30), the system will silently truncate the
`to` date to Jan 31, returning only the first 30 days of your requested period. No error is thrown.Configuration example
1POST {{fluentApiHost}}/graphql
2
3mutation CreateSetting {
4 createSetting(input: {
5 name: "fc.graphql.compatibility.articlesByLocation.maxSearchPeriodDays",
6 valueType: "INTEGER",
7 value: 60,
8 context: "ACCOUNT",
9 contextId: 0}) {
10 id
11 name
12 }
13}Update example
1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4 updateSetting(input: {
5 id: 5001464,
6 name: "fc.graphql.compatibility.articlesByLocation.maxSearchPeriodDays",
7 valueType: "INTEGER",
8 value: 45,
9 context: "ACCOUNT",
10 contextId: 0}) {
11 id
12 name
13 }
14}