Changes / Lever / Automation Workflows Not Triggering
Lever: Major incident: Automation Workflows Not Triggering
Summary
Lever reported a major incident affecting automation workflows in Global Data Center - LeverTRM - Hire, Hire: workflows were not triggering, then were confirmed to be processing with delays. The incident started at 2026-01-21 22:08 UTC and was resolved at 2026-01-22 16:04 UTC, lasting 17 h 56 min; no cause or specific fix was stated.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Automation Workflows Not Triggering
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-21 22:08 UTC
Before: not present
After: 2026-01-22 16:04 UTC
Before: not present
After: Global Data Center - LeverTRM - Hire, Hire
Before: not present
After: We became aware of an issue where automation workflows are not triggering starting around 1/21/2026 at 9:40am PT. We are currently investigating and will provide an update as soon as possible.
Before: not present
After: We are continuing to investigate this issue. We have found that automation workflows are still processing with a delay. New information will be shared as soon as possible.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: This issue has been resolved and our teams are monitoring to ensure continued stability
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Automation Workflows Not Triggering (this change) Lever reported a major incident affecting automation workflows in Global Data Center - LeverTRM - Hire, Hire: workflows were not triggering, then were confirmed to be processing with delays. The incident started at 2026-01-21 22:08 UTC and was resolved at 2026-01-22 16:04 UTC, lasting 17 h 56 min; no cause or specific fix was stated. | Major incident |