Nosto incident

CustomFields in Search and CM temporarily unavailable

Minor Resolved View vendor source →

Nosto experienced a minor incident on September 22, 2025 affecting Search & Categories, lasting 19h 20m. The incident has been resolved; the full update timeline is below.

Started
Sep 22, 2025, 07:05 PM UTC
Resolved
Sep 23, 2025, 02:26 PM UTC
Duration
19h 20m
Detected by Pingoru
Sep 22, 2025, 07:05 PM UTC

Affected components

Search & Categories

Update timeline

  1. monitoring Sep 22, 2025, 07:05 PM UTC

    We are currently experiencing an issue where some products in API responses are missing custom fields (returned as null). The source of the issue has been identified, and our team is actively working on restoring the service to ensure all product data is returned as expected. Further updates will be provided as we make progress.

  2. monitoring Sep 22, 2025, 10:17 PM UTC

    We have identified that SKU-level custom fields are impacted when products are updated. Our team is applying temporary fixes to address parts of the issue in the short term. In parallel, we are preparing longer-term solutions that will fully clean and restore the affected data. We will continue to work on these fixes and keep this incident updated as progress is made.

  3. monitoring Sep 23, 2025, 08:25 AM UTC

    We have identified the root cause of the issue affecting SKU-level custom fields in our Search product and have implemented a fix. Our team is now addressing any product data for all merchants using Search to ensure consistency across datasets. This process will be completed within the next few hours. Impact: * Only updated products were affected. * Missing data was limited primarily to SKU-level custom fields. * The total number of impacted products is relatively small, but we recognize that this may have caused undesired side effects in some cases. We appreciate your patience and understanding as we work to finalize data consistency across all merchants.

  4. resolved Sep 23, 2025, 02:26 PM UTC

    The product data has been restored to current up-to-date state