Vendor reports: operationalResolved · vendor status “resolved”Official status API

Postman Flows actions fail when triggered via webhook or schedule

Reported by Postman · Developer Tools & CI/CD · source last read just now

Official source (opens in a new tab)
Vendor start
Dec 17, 2025, 14:14 UTC
Vendor's clock
Resolved
Dec 17, 2025, 17:53 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 39 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Postman reports operational: "Postman Flows actions fail when triggered via webhook or schedule".[E1, E2]
  • The vendor marked it resolved at 2025-12-17 17:53 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-12-17 17:53 UTC · summary s1, evidence 6d2d3e49f221518f

Evidence (7)
  1. E1Postman reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Postman Flows actions fail when triggered via webhook or schedule". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-12-17 14:14 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-12-17 17:53 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Postman is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Dec 17, 2025, 14:14 UTCVendor-reported startVendor time
  2. Dec 17, 2025, 17:53 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.