Friction holds 14 sourced reports about Temporal (temporal.io) from 65 public source threads (as of 2026-10-15), and none says the author left. This page shows what its users say pushes them away, and the problem profile of n8n, Windmill.
Get started free with your email Open Temporal on Friction
The most-reported open problems, worst severity first. Each links to the item with its source.
NULL-to-string scan errors block workflows after upgrade to 1.27.0 · Self-hosting & upgrades · Blocks work · 3 people
“internal clients in a standalone, containerized Temporal service are unable to establish connections to the internal frontend service”
History service uses too much memory · Performance · Blocks work · 2 people
“This seems to be result in slow increase of cpu & memory usage eventually resulting in outage”
Stuck workflows show In Progress with errors only buried in event log · Reliability & bugs · Blocks work
“Workflows can sometimes hit a state where the status reads in progress and errors aren't reported anywhere except buried in the event log”
Stale internode gRPC connections to terminated pods on Kubernetes · Reliability & bugs · Annoyance · 3 people
“SWIM continuously pings these dead IPs, causing them to cycle alive→suspect→faulty indefinitely”
Matching service Prometheus metric cardinality grows without bound · Reporting & analytics · Annoyance
“Long-lived clusters should not see `scrape_samples_scraped` increase monotonically per matching pod purely as a function of pod uptime”
See all 14 themes for Temporal
Switching trades one set of problems for another. The same evidence, for each tool Friction covers in this category:
39 reports · 80 source threads · most-discussed area: Reliability & bugs
17 reports · 69 source threads · most-discussed area: Reliability & bugs
Counts and reports reflect people who post in public (developers and technical buyers are over-represented). A tool with fewer reports is not a better tool; it may only be discussed less. How the data is built.