Contentful: Strict validation of skip, limit and include query parameters
Timeline of updates
- resolved
Due to a misconfiguration in our feature-flagging system we accidentally rolled out a breaking change to small percentage of our customers without advanced notice. The change involved stricter validation of skip, limit and include query parameters to clarify which values are supported and used. We’ve put additional internal safeguards in place to prevent this from happening again.
From Contentful’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.contentfulstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Contentful, started 2017-01-04 11:01 UTC, resolved after 0 min, 1 update(s).
- Title
- Strict validation of skip, limit and include query parameters
- Vendor
- Contentful
- Date
- URL
- https://rewindex.com/company/contentful/incidents/31x8jfkh7vrr
Contentful profileRecent Contentful incidentsAll outages on January 4, 2017Contentful in January 2017MarkdownJSON