Rewindex

CompaniesCriblIncidents

Cribl: Increase in errors in code function following 4.17.0 release

MajorStatus: resolvedStarted Resolved (23 h)9 updatesstspg.io (opens in new tab)

Timeline of updates

  1. investigating

    We are currently investigating this issue.

  2. investigating

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  3. investigating

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  4. investigating

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  5. investigating

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the half hour.

  6. investigating

    We are investigating an increase in errors with Code Function. The actual impact to data is unknown at this time. We will post an update at the top of the hour.

  7. investigating

    We have confirmed that the recent increase in Code Function errors did not impact overall data flow. We identified an issue with recursive Code Function executions temporarily blocking throughput for a small number of customers. We have worked directly with the affected users to mitigate and stabilize their pipelines, and systems are operating as expected at this time and we are contiuing to monitor all signals.

  8. monitoring

    A fix has been implemented and we are monitoring the results.

  9. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

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 stspg.io (opens in new tab).

Cribl profileRecent Cribl incidentsMarkdownJSON