rewindex

CompaniesFireHydrantIncidents

FireHydrant: Incident Types Not Working on Desktop Slack

MinorStatus: resolvedStarted Resolved (4 d)5 updatesstatus.firehydrant.com (opens in new tab)

Affected components: Slack

Timeline of updates

  1. resolved

    Incident types are not working for a subset of customers in Slack and the web ui. We are investigating the root cause of the issue. Incident declaration continues to function as normal otherwise. Please continue to fill out fields as needed.

  2. resolved

    We have identified an issue with how Slack is rendering incident type field modal confirmations on mobile vs desktop. We are testing a fix now and creating an urgent support ticket to Slack. We have confirmed the web ui works as expected.

    Please use the web ui if using incident types. Incident declaration still works within Slack without incident types

  3. resolved

    We have confirmed that incident types are only negatively affected on Slack desktop. Slack mobile and the Web UI remain unaffected.

    Incident types still work as expected for Slack mobile and the Web UI. Incident declaration continues to work on all surfaces.

    An urgent support ticket has been filed with our upstream provider, Slack, on how they are rendering form inputs and confirmations for desktop.

  4. resolved

    We have confirmed that this is an issue with our upstream provider, Slack, and continue to monitor our communication channels with them.

    Incident types continue to work as expected on mobile as well as the web ui. Incident declaration continues to work on all surfaces although incident types may need to be added after declaration

  5. resolved

    We have confirmed with our upstream provider, Slack, that the issue has been resolved on their end. All incident types are working as expected on mobile and desktop. We apologize for any inconvenience this may have caused

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 status.firehydrant.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by FireHydrant, started 2025-10-10 13:05 UTC, resolved after 4 d, 5 update(s).

Title
Incident Types Not Working on Desktop Slack
Vendor
FireHydrant
Date
URL
https://rewindex.com/company/firehydrant/incidents/ae464ee0-e056-44d1-92fc-2e8f66b8e917

FireHydrant profileRecent FireHydrant incidentsAll outages on October 10, 2025FireHydrant in October 2025MarkdownJSON