[{"data":1,"prerenderedAt":1454},["ShallowReactive",2],{"blog-\u002Fblog\u002F2025\u002F12\u002Ffive-whys-root-cause-analysis-definition-examples":3,"featureCatalog":524,"changelog-titles":919,"blog-all-for-related":1453},{"id":4,"title":5,"authors":6,"body":8,"cta":503,"date":504,"description":505,"extension":506,"features":503,"image":507,"lastUpdated":508,"meta":509,"navigation":514,"path":515,"release":503,"seo":516,"sitemap":517,"stem":518,"subtitle":519,"tags":520,"tldr":522,"video":503,"__hash__":523},"blog\u002Fblog\u002F2025\u002F12\u002Ffive-whys-root-cause-analysis-definition-examples.md","Five Whys Root Cause Analysis: Definition, Steps & Examples (2026)",[7],"sumit-shinde",{"type":9,"value":10,"toc":482},"minimark",[11,15,18,21,26,29,32,35,42,46,67,70,73,76,80,83,86,121,125,128,138,141,144,147,150,153,156,160,163,166,169,172,176,190,205,208,211,215,218,221,224,227,230,234,237,240,243,246,250,253,256,259,262,265,269,272,275,278,282,285,291,304,315,326,337,348,354,360,363,367,370,373,376,379,382,386,389,395,401,407,413,417,420,423,426,429,432,435,439,442,445,448,451,454,457,461,464,471,474],[12,13,14],"p",{},"The Five Whys is a root cause analysis technique where you ask \"why\" repeatedly, typically five times, until you identify the underlying systemic cause instead of just symptoms.",[12,16,17],{},"Your equipment fails on Tuesday. The maintenance team fixes it. It fails again on Friday. They fix it again. Three weeks later, same failure. This cycle continues because everyone treats the symptom, the broken part, instead of asking why it broke.",[12,19,20],{},"The Five Whys breaks this pattern. Developed by Sakichi Toyoda at Toyota in the 1930s, it's become the standard root cause analysis method across manufacturing, healthcare, software development, and anywhere recurring problems drain productivity. The technique works through systematic questioning that strips away symptoms to expose fixable failures in your systems, the process gaps, training deficiencies, and procedural weaknesses that allow problems to persist. When applied correctly, it takes under an hour and prevents problems from returning.",[22,23,25],"h2",{"id":24},"what-is-the-five-whys-root-cause-analysis-method","What Is the Five Whys Root Cause Analysis Method?",[12,27,28],{},"The Five Whys root cause analysis is a questioning technique where you ask \"why\" a problem occurred, then ask \"why\" that condition existed, then keep asking until you hit something you can actually fix at a systemic level. It was developed by Sakichi Toyoda in the 1930s and became a core tool in the Toyota Production System. Today it's used across manufacturing, healthcare, software development, and anywhere else people need to solve recurring problems.",[12,30,31],{},"The technique is deceptively simple. You start with a specific problem. You ask why it happened. You take that answer and ask why again. You keep going until asking \"why\" one more time would just be splitting hairs or rehashing what you already know. Usually that takes about five iterations, the number comes from the observation that five whys is typically sufficient to reveal the root cause, but I've seen effective analyses that stopped at three and others that went to eight.",[12,33,34],{},"Watch this video if you prefer video format:",[36,37],"lite-youtube",{"videoid":38,"params":39,"style":40,"title":41},"-_nN_YTDsuk","rel=0","margin-top: 20px; margin-bottom: 20px; width: 100%; height: 480px;","YouTube video player",[22,43,45],{"id":44},"why-the-five-whys-works-when-other-methods-dont","Why the Five Whys Works When Other Methods Don't",[12,47,48,49,56,57,61,62,66],{},"Organizations often spend weeks on elaborate root cause analyses using ",[50,51,55],"a",{"href":52,"rel":53},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FFault_tree_analysis",[54],"nofollow","fault trees",", ",[50,58,60],{"href":59},"\u002Fblog\u002F2026\u002F07\u002Fishikawa-fishbone-diagram\u002F","fishbone diagrams",", and ",[50,63,65],{"href":64},"\u002Fblog\u002F2025\u002F07\u002Fquality-control-automation-spc-charts","statistical process control charts",", only to implement solutions that don't stick. The Five Whys succeeds where these methods often fail for three reasons.",[12,68,69],{},"First, it's fast. You can complete a thorough analysis in under an hour. That speed matters because problems are freshest when they just happened. Witnesses remember details. Physical evidence hasn't been cleaned up or moved. The sense of urgency is still there. Wait two weeks to schedule your analysis meeting, and you're working from memory and assumptions.",[12,71,72],{},"Second, it's accessible. The machine operator who saw the problem doesn't need training in statistical methods or failure mode analysis. They just need to answer questions honestly about what they observed. This democratization of problem-solving means you're not waiting for specialists to free up their calendars. The people closest to the work can solve problems themselves.",[12,74,75],{},"Third, it forces you to follow a single causal chain all the way down. Other methods encourage you to map out every possible contributing factor simultaneously. That comprehensiveness sounds good in theory, but in practice it often leads to analysis paralysis. You've identified seventeen potential causes, and now you're trying to fix all of them at once. The Five Whys makes you pick the most likely path and follow it to the end. You can always come back and explore alternative explanations if your first solution doesn't work.",[22,77,79],{"id":78},"the-five-whys-checklist-what-you-need-before-you-start","The Five Whys Checklist: What You Need Before You Start",[12,81,82],{},"Most failed Five Whys sessions fail before they even begin because people skip the setup. You need four things in place before you ask the first question.",[12,84,85],{},"Before you ask the first question, you need four things:",[87,88,89,97,103,115],"ul",{},[90,91,92,96],"li",{},[93,94,95],"strong",{},"A specific problem statement."," \"Quality issues in Department B\" won't work. \"Thirty-seven units failed final inspection on December 18th due to incomplete welds\" will. Specificity disciplines your thinking and keeps the analysis focused.",[90,98,99,102],{},[93,100,101],{},"The right people."," That means at least one person who directly observed or experienced the problem, someone who understands the process well enough to spot abnormal conditions, and a facilitator who can keep the questions moving forward. Three to five people is ideal. More than that and you'll spend more time managing the discussion than conducting the analysis.",[90,104,105,108,109,114],{},[93,106,107],{},"Location at the gemba."," Conduct the analysis close to where the problem occurred. This principle, which Toyota calls ",[50,110,113],{"href":111,"rel":112},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FGemba",[54],"gemba",", matters more than most people realize. Conference rooms encourage abstract thinking. The shop floor, the customer service desk, or the server room keeps everyone grounded in physical reality. You can point at things. You can test hypotheses on the spot.",[90,116,117,120],{},[93,118,119],{},"Commitment to honest answers."," If the real reason your new hires keep making mistakes is that your training program is inadequate, you need people willing to say that out loud. If your preventive maintenance schedule was designed fifteen years ago and never updated, someone needs to acknowledge it. The Five Whys only works if people tell the truth about what they see.",[22,122,124],{"id":123},"how-to-complete-a-five-whys-root-cause-analysis","How to Complete a Five Whys Root Cause Analysis",[12,126,127],{},"The mechanics of the method are straightforward, but execution requires more care than most people expect.",[12,129,130,135],{},[131,132],"img",{"alt":133,"src":134},"Five Whys funnel diagram from problem to root cause","\u002Fblog\u002F2025\u002F12\u002Fimages\u002F5-Why-Funnel.jpg",[136,137,133],"em",{},[12,139,140],{},"Start by stating the problem as precisely as you can. Write it down where everyone can see it. If you're working through this at the gemba, write it on a whiteboard or a large sheet of paper. If you're remote, put it in a shared document. The problem statement anchors everything that follows, so take the time to get it right. Include what happened, when it happened, where it happened, and how you know it happened. Measurements matter here. \"Production was slow\" is too vague. \"Line 3 produced 847 units against a target of 1,000 units during the first shift on December 20th\" gives you something concrete to investigate.",[12,142,143],{},"Ask your first why: Why did this specific problem occur? The answer should be factual, not speculative. \"I think maybe the bearings were worn\" isn't good enough. \"The motor seized, and when we disassembled it, we found metal shavings in the bearing housing\" is what you're after. If you don't know the answer with certainty, stop and gather evidence before continuing.",[12,145,146],{},"Take that answer and ask why again. Why did the motor bearings fail? Because the lubrication system wasn't delivering oil to that bearing. How do you know? Because we checked the oil flow and found the feed line was clogged. This is where many analyses go wrong. People start speculating instead of observing. They say things like \"probably the operator forgot to check it\" when what they actually know is that the line was clogged. Stick to what you can verify.",[12,148,149],{},"Continue this pattern. Each answer becomes the subject of the next question. Why was the feed line clogged? Because particulate from the oil reservoir got into the line. Why was there particulate in the reservoir? Because we're not filtering the oil when we top off the reservoir. Why aren't we filtering it? Because the maintenance procedure doesn't specify using a filter when adding oil.",[12,151,152],{},"Stop when you've identified a process failure or systemic gap. In this case, the inadequate maintenance procedure is your root cause. It's something you can fix with a clear corrective action: revise the maintenance procedure to require filtered oil and provide the appropriate filtering equipment. That's different from \"operator error\" or \"equipment failure,\" which are symptoms, not causes.",[12,154,155],{},"Notice that this example took exactly five questions, but that's coincidental. Effective analyses sometimes reach the root cause in three questions and other times need eight. The number doesn't matter. What matters is reaching the point where you've identified something you can actually fix.",[22,157,159],{"id":158},"when-and-where-should-you-use-the-five-whys","When and Where Should You Use the Five Whys?",[12,161,162],{},"The Five Whys is particularly effective for problems with a dominant causal chain. If your problem has one primary cause with some contributing factors, this method will find it quickly. It works well for equipment failures, quality defects, process bottlenecks, safety incidents, and customer complaints where you're trying to understand what broke down in your systems.",[12,164,165],{},"It's less effective for complex problems with multiple simultaneous causes that interact with each other. If you're investigating a major product recall with contributing factors spanning design, materials, manufacturing, and distribution, the Five Whys will feel inadequate. You're better off with something like fishbone analysis or fault tree analysis that lets you map multiple causal pathways simultaneously.",[12,167,168],{},"The method also struggles with problems that have deep organizational or cultural roots. If your real issue is that nobody wants to report problems because they fear retaliation, asking \"why\" five times might surface that fact, but fixing it requires organizational change management that's well beyond what a questioning technique can address. The Five Whys can identify the issue, but you'll need other tools to solve it.",[12,170,171],{},"The method works well for equipment failures and maintenance issues, quality problems that recur despite corrections, process bottlenecks that resist obvious solutions, safety incidents requiring rapid investigation, and customer complaints where you need to fix internal processes. It struggles with problems that have multiple independent causes, new product development scenarios where you're trying to prevent future failures, strategic planning issues, and situations where participants don't have sufficient knowledge to answer accurately.",[22,173,175],{"id":174},"the-toyota-five-whys-where-this-method-came-from","The Toyota Five Whys: Where This Method Came From",[12,177,178,183,184,189],{},[50,179,182],{"href":180,"rel":181},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSakichi_Toyoda",[54],"Sakichi Toyoda"," developed the Five Whys in the 1930s as part of the manufacturing methodology that would eventually become the ",[50,185,188],{"href":186,"rel":187},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FToyota_Production_System",[54],"Toyota Production System",". Toyoda, who founded what would become Toyota Industries, was obsessed with understanding why things failed. His approach was radical for its time: instead of accepting problems as inevitable, he insisted they were symptoms of deeper issues that could be identified and eliminated.",[12,191,192,193,198,199,204],{},"His son ",[50,194,197],{"href":195,"rel":196},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKiichiro_Toyoda",[54],"Kiichiro Toyoda"," and engineer ",[50,200,203],{"href":201,"rel":202},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FTaiichi_Ohno",[54],"Taiichi Ohno"," refined the method as they developed Toyota's production system in the decades after World War II. They formalized the practice of going to the gemba to observe problems firsthand and asking why until you hit something systemic rather than symptomatic.",[12,206,207],{},"Toyota's success with this approach attracted attention in the 1970s and 1980s when Western manufacturers were trying to understand why Japanese companies were outcompeting them. The Five Whys spread beyond automotive manufacturing into other industries, though often without the cultural foundation that made it effective at Toyota. Many companies adopted the technique as a standalone tool without understanding that it only works in an environment where people feel safe identifying systemic problems and where management is committed to fixing them.",[12,209,210],{},"That context matters when you're implementing the Five Whys in your organization. The technique itself is simple, but it won't survive in a culture that shoots the messenger or treats problem identification as complaining rather than continuous improvement.",[22,212,214],{"id":213},"best-practices-from-experienced-root-cause-analysis","Best Practices From Experienced Root Cause Analysis",[12,216,217],{},"Focus on processes and systems, not people. When your analysis points to an individual who made a mistake, don't stop there. Ask why that mistake was possible. Why didn't training cover this situation? Why didn't the procedure include a verification step? Why wasn't there a physical or administrative control that would have caught the error? Robust processes assume people will make mistakes and build in safeguards. If your process allows one person's mistake to cause a significant problem, your process is inadequate.",[12,219,220],{},"Verify every answer before moving to the next question. The Five Whys fails when it becomes an exercise in brainstorming rather than investigation. Each answer should be based on evidence you can point to: physical observations, data from sensors or logs, documents, measurements, or direct testimony from witnesses. If your team is guessing, stop and gather facts.",[12,222,223],{},"Stay on one causal chain at a time. Real problems often have multiple contributing causes, and your team will want to explore all of them simultaneously. Resist this. Follow the most likely path all the way to the end first. If the corrective actions you implement don't solve the problem, you can come back and explore alternative paths. Trying to investigate everything at once creates confusion and dilutes your focus.",[12,225,226],{},"Keep your questions neutral. \"Why did the operator forget to check the pressure?\" assumes forgetfulness and points toward blame. \"Why wasn't the pressure checked?\" opens up multiple possibilities including procedural gaps, time pressure, distraction, inadequate training, or unclear responsibility. How you phrase the question shapes what answers you'll get.",[12,228,229],{},"Know when to stop. You've found your root cause when the answer identifies something you can fix through a procedural change, a training modification, a design improvement, or another corrective action that addresses the systemic level. If you keep asking why beyond that point, you'll end up with philosophical answers about organizational culture or budget constraints that aren't actionable in the context of this specific problem.",[22,231,233],{"id":232},"common-mistakes-that-undermine-five-whys-analysis","Common Mistakes That Undermine Five Whys Analysis",[12,235,236],{},"The most frequent mistake is stopping at symptoms. A part fails, and the team replaces it, logs \"component failure\" as the root cause, and moves on. That's not root cause analysis. That's just describing what happened. The root cause is why the component failed: inadequate maintenance, incorrect installation, design limitation, contamination, or some other systemic issue that made the failure possible.",[12,238,239],{},"Another common failure is accepting \"human error\" as a root cause. People make mistakes. This is not new information. If your analysis concludes that someone made a mistake, ask why that mistake was possible and why existing safeguards didn't prevent or catch it. Human error is a symptom, not a cause.",[12,241,242],{},"Teams sometimes rush through the analysis because they're uncomfortable with the questions. Someone asks why a procedure wasn't followed, and instead of actually investigating, the team quickly blames the operator and moves on. This happens in organizations where problem-solving has become a blame-finding exercise. If your culture doesn't support honest answers, the Five Whys won't work regardless of how well you understand the technique.",[12,244,245],{},"Some teams branch off into multiple causal chains without finishing any of them. They ask the first why, get an answer, then immediately see three more potential causes and start investigating all of them. Before long, they've filled a whiteboard with possibilities but haven't followed any single path to a concrete root cause. Discipline yourself to investigate one chain completely before exploring alternatives.",[22,247,249],{"id":248},"tools-and-software-for-five-whys-analysis","Tools and Software for Five Whys Analysis",[12,251,252],{},"You don't need specialized software to conduct a Five Whys analysis. A whiteboard, a notepad, or a simple word processing document works fine. The tool matters far less than the discipline with which you apply the method.",[12,254,255],{},"That said, organizations that conduct frequent root cause analyses often find value in standardized digital tools. Quality management systems like ETQ, MasterControl, or Sparta Systems include Five Whys templates integrated with corrective action tracking. This integration helps ensure that the actions identified during analysis actually get completed and verified.",[12,257,258],{},"Project management platforms can be adapted for Five Whys documentation if you configure custom workflows. The advantage here is that corrective actions automatically flow into your existing task management processes rather than living in a separate system that nobody checks.",[12,260,261],{},"Some organizations prefer physical tools. I've worked in plants that keep Five Whys templates on clipboards at each production line. When a problem occurs, the shift supervisor conducts the analysis right there, documents it on the physical form, and posts it on a problem-solving board where everyone can see it. This visibility reinforces the importance of root cause analysis and shares lessons learned across shifts.",[12,263,264],{},"The best tool is the one your team will actually use consistently. If your organization already has a quality management system, use that. If you're just starting out, begin with the simplest thing that works: a shared document template and a commitment to complete one analysis per week.",[22,266,268],{"id":267},"what-is-the-5-problem-solving-steps-process","What Is the 5 Problem-Solving Steps Process?",[12,270,271],{},"The 5 problem-solving steps is a broader framework that incorporates the Five Whys as one component. The steps are: define the problem, analyze the root cause, develop solutions, implement corrective actions, and verify effectiveness. The Five Whys specifically addresses the second step, root cause analysis.",[12,273,274],{},"This framework matters because root cause analysis by itself doesn't solve problems. You also need clear problem definition up front, solution development after you identify the cause, disciplined implementation, and verification that your corrective actions actually worked. Organizations sometimes do excellent Five Whys analyses but never implement the corrective actions they identify. The analysis becomes an end in itself rather than a means to improvement.",[12,276,277],{},"Effective problem-solving requires all five steps in sequence. Rushing to solutions before you understand root causes leads to wasted effort fixing the wrong things. Identifying root causes but failing to implement solutions means nothing changes. Implementing solutions without verification means you never know if they actually worked or if the problem just hasn't recurred yet by chance.",[22,279,281],{"id":280},"example-of-a-5-why-question-in-practice","Example of a 5 Why Question in Practice",[12,283,284],{},"What does an effective Five Whys question actually sound like? Here's the classic example from Taiichi Ohno, one of the architects of the Toyota Production System, documented in his book \"Toyota Production System: Beyond Large-Scale Production\" (1988, p. 17).",[12,286,287,290],{},[93,288,289],{},"The problem:"," A machine stopped functioning on the factory floor.",[12,292,293,296,297,300,303],{},[93,294,295],{},"Why #1:"," \"Why did the machine stop?\"",[298,299],"br",{},[136,301,302],{},"Answer:"," There was an overload and the fuse blew.",[12,305,306,309,310,312,314],{},[93,307,308],{},"Why #2:"," \"Why was there an overload?\"",[298,311],{},[136,313,302],{}," The bearing was not sufficiently lubricated.",[12,316,317,320,321,323,325],{},[93,318,319],{},"Why #3:"," \"Why was it not lubricated sufficiently?\"",[298,322],{},[136,324,302],{}," The lubrication pump was not pumping sufficiently.",[12,327,328,331,332,334,336],{},[93,329,330],{},"Why #4:"," \"Why was it not pumping sufficiently?\"",[298,333],{},[136,335,302],{}," The shaft of the pump was worn and rattling.",[12,338,339,342,343,345,347],{},[93,340,341],{},"Why #5:"," \"Why was the shaft worn out?\"",[298,344],{},[136,346,302],{}," There was no strainer attached and metal scrap got in.",[12,349,350,353],{},[93,351,352],{},"Root cause:"," No strainer in the lubrication system allowing debris contamination.",[12,355,356,359],{},[93,357,358],{},"Corrective action:"," Install a strainer in the lubrication system to prevent metal scrap from entering the pump.",[12,361,362],{},"This example demonstrates the fundamental questioning pattern. Modern Five Whys analyses typically include more detailed evidence documentation at each step (inspection reports, sensor data, maintenance logs), but the core approach of following a single causal chain to reach a systemic issue remains unchanged. Notice how the analysis moved from a symptom (blown fuse) through intermediate causes (overload, insufficient lubrication, worn shaft) to arrive at a fixable process gap (missing strainer).",[22,364,366],{"id":365},"implementing-the-five-whys-in-your-organization","Implementing the Five Whys in Your Organization",[12,368,369],{},"If you want to implement the Five Whys effectively, start with a pilot program rather than a company-wide rollout. Select one department or one type of problem as your initial focus. Train a small group of people thoroughly rather than providing superficial training to everyone. Conduct your first few analyses with experienced facilitation, ideally from someone who has used the method successfully in another organization.",[12,371,372],{},"Expect the first several analyses to feel awkward. People will struggle with phrasing neutral questions. They'll want to skip ahead to solutions before finishing the analysis. They'll be uncomfortable when the questioning reveals gaps in procedures or training. This is normal. The skill develops with practice.",[12,374,375],{},"After each analysis, conduct a brief debrief focused on the process itself. What went well? Where did we struggle? Did we gather evidence before answering, or did we speculate? Did we follow one causal chain to the end, or did we branch off into multiple paths? This reflection builds capability faster than simply conducting more analyses.",[12,377,378],{},"Track your corrective action completion rate. If actions identified during Five Whys analyses aren't being implemented, you have an organizational problem that needs attention. Root cause analysis without follow-through is worse than no analysis at all because it creates the illusion of improvement while nothing actually changes.",[12,380,381],{},"Give it six months before evaluating whether the method is working for your organization. You should see a reduction in recurring problems, faster resolution of new problems, and increasing confidence among frontline staff in their ability to identify and solve issues. If you're not seeing these outcomes, the problem is usually implementation rather than the method itself.",[22,383,385],{"id":384},"measuring-whether-the-five-whys-is-working","Measuring Whether the Five Whys Is Working",[12,387,388],{},"How do you know if the Five Whys is actually improving your operations? Four metrics tell the story:",[12,390,391,394],{},[93,392,393],{},"Problem recurrence rates."," If you're conducting thorough root cause analyses and implementing effective corrective actions, the same problems should stop reappearing. Pull your incident data from six months before you started using the Five Whys and compare it to six months after. Look for problems that used to recur monthly or quarterly that have stopped appearing.",[12,396,397,400],{},[93,398,399],{},"Cycle time from problem to solution."," As your team gets more practiced with the method, this should decrease. Early on, you might take two weeks to complete an analysis and implement corrections. After several months of practice, you should be conducting same-day or next-day analyses with corrective actions implemented within a week.",[12,402,403,406],{},[93,404,405],{},"Quality of corrective actions."," Are you implementing procedural changes, training improvements, and system modifications? Or are you repeatedly concluding that operators need to \"be more careful\" and issuing reminders? High-quality corrective actions address systemic issues. Low-quality corrective actions ask people to try harder without changing anything about the system they work in.",[12,408,409,412],{},[93,410,411],{},"Staff engagement."," Are frontline staff bringing problems forward more readily? Are they participating actively in analyses? Are they suggesting root causes and corrective actions? Increasing engagement signals that the method is building problem-solving capability across your organization rather than remaining a management-only activity.",[22,414,416],{"id":415},"the-limitations-nobody-talks-about","The Limitations Nobody Talks About",[12,418,419],{},"The Five Whys has limitations that don't get discussed much in the literature promoting it. Understanding these limitations helps you apply the method appropriately rather than treating it as a universal solution.",[12,421,422],{},"First, the method assumes a relatively linear cause-and-effect relationship. Many real-world problems involve complex interactions between multiple systems where causes and effects aren't clearly distinguishable. Equipment failures in modern automated systems often result from software interactions, sensor drift, mechanical wear, and operator actions all contributing simultaneously. The Five Whys struggles with this kind of complexity because it forces you to follow a single thread.",[12,424,425],{},"Second, the technique depends entirely on the knowledge and honesty of the people answering the questions. If they don't actually know why something happened, they'll speculate. If they're afraid of identifying systemic issues that might reflect poorly on management, they'll stop at superficial answers. The Five Whys doesn't magically generate insight. It structures questioning, but the quality of answers depends on the people providing them.",[12,427,428],{},"Third, the method can lead to what statisticians call \"confirmation bias.\" If your team already suspects the cause of a problem, the questions will unconsciously steer toward confirming that hypothesis rather than genuinely exploring alternatives. A facilitator aware of this bias can counteract it, but it requires conscious effort.",[12,430,431],{},"Finally, the Five Whys doesn't help you prioritize which problems to investigate. If you have twenty recurring issues, it doesn't tell you which five deserve immediate root cause analysis and which can wait. You need a separate prioritization framework based on safety risk, financial impact, frequency, or strategic importance.",[12,433,434],{},"These limitations don't make the method useless. They just mean you need to recognize when you're facing a problem that requires a different or additional approach.",[22,436,438],{"id":437},"what-happens-after-the-analysis","What Happens After the Analysis",[12,440,441],{},"The Five Whys analysis is the easy part. Implementation is where most organizations struggle. You've identified that your preventive maintenance schedule is inadequate, or your training program has gaps, or your procedures haven't been updated to match your current equipment. Now you have to actually fix these things, which requires resources, time, and organizational commitment.",[12,443,444],{},"Effective implementation requires clear ownership. Someone needs to be specifically responsible for each corrective action, with a realistic deadline and the authority to make the necessary changes. \"The maintenance department will handle it\" doesn't work. \"James will revise the PM schedule by December 15th and review it with the maintenance manager before implementation\" does.",[12,446,447],{},"Build verification into your corrective actions. How will you know if the changes you implemented actually solved the problem? In some cases, verification is straightforward: if the problem was equipment failures, track whether failures stop occurring. In other cases, you need to actively test: if you revised a procedure, observe someone following the new procedure to ensure it's clear and complete.",[12,449,450],{},"Communicate the results. When a Five Whys analysis leads to improvements, tell people about it. Post the analysis and the corrective actions where staff can see them. Mention it in team meetings. This visibility serves two purposes: it demonstrates that problem-solving leads to real changes, and it shares lessons learned across your organization so other areas can benefit from what you discovered.",[12,452,453],{},"Don't declare victory too soon. Some corrective actions take time to show results, and some problems are intermittent enough that you need several months of data to confirm they're truly resolved. Plan a follow-up review three to six months after implementation to verify effectiveness and make adjustments if needed.",[12,455,456],{},"The Five Whys is a tool for getting to root causes. But getting to root causes only matters if you do something about them. The analysis takes thirty minutes. The real work comes after.",[22,458,460],{"id":459},"monitor-your-corrective-actions-across-all-systems","Monitor Your Corrective Actions Across All Systems",[12,462,463],{},"You've identified the root cause and implemented fixes. Now you need to verify they're working, across IT systems, OT equipment, quality databases, and maintenance platforms.",[12,465,466,470],{},[50,467,469],{"href":468},"\u002F","FlowFuse"," connects them all. Whether it's legacy PLCs or modern IoT sensors, ERP systems or SCADA networks, FlowFuse brings your data together in one place. Build dashboards that track the metrics proving your solutions worked: reduced equipment failures, lower defect rates, improved maintenance compliance, or whatever KPIs matter for your specific corrective actions.",[12,472,473],{},"Catch warning signs before problems recur. See trends that reveal whether your fixes are holding or degrading over time. Turn root cause analysis into continuous improvement with real-time monitoring.",[12,475,476,481],{},[50,477,480],{"href":478,"rel":479},"https:\u002F\u002Fapp.flowfuse.com",[54],"Start connecting your systems with FlowFuse"," and prove your Five Whys analyses deliver lasting results.",{"title":483,"searchDepth":484,"depth":484,"links":485},"",4,[486,488,489,490,491,492,493,494,495,496,497,498,499,500,501,502],{"id":24,"depth":487,"text":25},2,{"id":44,"depth":487,"text":45},{"id":78,"depth":487,"text":79},{"id":123,"depth":487,"text":124},{"id":158,"depth":487,"text":159},{"id":174,"depth":487,"text":175},{"id":213,"depth":487,"text":214},{"id":232,"depth":487,"text":233},{"id":248,"depth":487,"text":249},{"id":267,"depth":487,"text":268},{"id":280,"depth":487,"text":281},{"id":365,"depth":487,"text":366},{"id":384,"depth":487,"text":385},{"id":415,"depth":487,"text":416},{"id":437,"depth":487,"text":438},{"id":459,"depth":487,"text":460},null,"2025-12-22","Learn the five Whys root cause analysis method in 2026: step-by-step process, real examples from Toyota, templates, and best practices to solve recurring problems permanently.","md","\u002Fblog\u002F2025\u002F12\u002Fimages\u002Ffive-whys-analysis.png","2025-12-23",{"keywords":503,"excerpt":510},{"type":9,"value":511},[512],[12,513,14],{},true,"\u002Fblog\u002F2025\u002F12\u002Ffive-whys-root-cause-analysis-definition-examples",{"title":5,"description":505},{"loc":515},"blog\u002F2025\u002F12\u002Ffive-whys-root-cause-analysis-definition-examples","A proven root cause analysis technique for solving recurring problems in manufacturing, operations, and continuous improvement.",[521],"flowfuse","The Five Whys is a root cause analysis technique developed at Toyota that involves repeatedly asking 'why' a problem occurred typically five times until you uncover a systemic, fixable cause rather than just a symptom. It works because it's fast, accessible to front-line workers without statistical training, and forces a single causal chain to its end. Applying it correctly prevents problems from recurring by targeting the process gaps, training deficiencies, or procedural weaknesses that allowed the failure in the first place.","s7bfqi9-shu1uNisrWNi3cR0wE-82sQbUIQhzoS7YZ8",{"id":525,"extension":526,"meta":527,"sections":528,"stem":917,"__hash__":918},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[529,580,681,743,820,899],{"id":530,"title":531,"features":532},"ai-automation","AI & Automation",[533,543,553,563,569,575],{"id":534,"title":535,"description":536,"docsLink":537,"changelog":538,"tiers":542},"flowfuse-expert-ai","FlowFuse Expert AI","Build industrial apps with agents, and query the state of the factory with an agent. Adapt your current hardware and machines so agentic work can be done against them, without ripping and replacing what's already on the plant floor.","\u002Fdocs\u002Fuser\u002Fexpert\u002F",[539],{"url":540,"release":541},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":514,"hub":514,"fleet":514},{"id":544,"title":545,"description":546,"docsLink":547,"changelog":548,"subfeature":514,"showOnPricing":551,"tiers":552},"flowfuse-expert-support-mode","Support Mode","Chat-based assistance for FlowFuse and Node-RED, including Node-RED instance management through natural language.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#support-mode",[549],{"url":550,"release":541},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":514,"hub":514,"fleet":514},{"id":554,"title":555,"description":556,"docsLink":557,"changelog":558,"subfeature":514,"showOnPricing":551,"tiers":562},"flowfuse-expert-application-building","Application Building","Describe what you want to build and FlowFuse Expert assembles it on your workspace, adding tabs, wiring nodes, and configuring properties.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F",[559],{"url":560,"release":561},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":514,"hub":514,"fleet":514},{"id":564,"title":565,"description":566,"docsLink":567,"subfeature":514,"beta":514,"showOnPricing":551,"tiers":568},"flowfuse-expert-insights-mode","Insights Mode","Connects FlowFuse Expert to MCP servers in your Node-RED instances, enabling real-time data queries and actions through a single chat interface.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#insights-mode",{"edge":514,"hub":514,"fleet":514},{"id":570,"title":571,"description":572,"docsLink":573,"tiers":574},"mcp-servers","Agentic Operations","Expose your Node-RED flows as tools an AI agent can call directly, so agents can query the state of the factory or trigger actions without custom integration work.","\u002Fnode-red\u002Fflowfuse\u002Fmcp\u002F",{"edge":514,"hub":514,"fleet":514},{"id":576,"title":577,"description":578,"tiers":579},"onnx-integration","ONNX Integration","Run trained machine learning models directly in your flows, including on edge hardware, without sending data out to an external inference service.",{"edge":514,"hub":514,"fleet":514},{"id":581,"title":582,"features":583},"build","Build",[584,590,596,606,612,618,622,628,634,642,648,652,656,665,673],{"id":585,"title":586,"description":587,"docsLink":588,"tiers":589},"edge-development","Edge Development","Develop and test Node-RED flows directly on edge devices with a remote editor proxy.","\u002Fdocs\u002Fdevice-agent\u002Fquickstart\u002F",{"edge":514,"hub":551,"fleet":514},{"id":591,"title":592,"description":593,"docsLink":594,"tiers":595},"private-npm-registry","Custom Node-RED Nodes","Create and manage your own private npm registry for Node-RED nodes, so you can share custom nodes across your team and devices without publishing them publicly.","\u002Fdocs\u002Fuser\u002Fcustom-npm-packages\u002F",{"edge":514,"hub":514,"fleet":514},{"id":597,"title":598,"description":599,"docsLink":600,"changelog":601,"tiers":605},"flowfuse-tables","FlowFuse Tables","A managed PostgreSQL database for every application, so you can store and query structured data without standing up and maintaining your own database.","\u002Fdocs\u002Fuser\u002Fff-tables\u002F",[602],{"url":603,"release":604},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":514,"hub":514,"fleet":514},{"id":607,"title":608,"description":609,"docsLink":610,"tiers":611},"persistent-files","File Storage","Store and retrieve files from your Node-RED flows, with automatic replication and backup across your devices and hosted instances.","\u002Fdocs\u002Finstall\u002Ffile-storage\u002F",{"edge":514,"hub":514,"fleet":514},{"id":613,"title":614,"description":615,"docsLink":616,"showOnPricing":551,"tiers":617},"persistent-context","Persistent Context","In-memory values defined in a Node-RED flow persist across project restarts and upgrades.","\u002Fdocs\u002Fuser\u002Fpersistent-context\u002F",{"edge":514,"hub":514,"fleet":514},{"id":619,"title":620,"showOnPricing":551,"tiers":621},"static-assets","Static Assets",{"edge":514,"hub":514,"fleet":514},{"id":623,"title":624,"description":625,"docsLink":626,"tiers":627},"team-library","Team Library","Set up standard nodes and flows that can be shared with all team members across your organisation.","\u002Fdocs\u002Fuser\u002Fshared-library\u002F",{"edge":514,"hub":514,"fleet":514},{"id":629,"title":630,"description":631,"docsLink":632,"tiers":633},"personalised-multi-user-dashboards","Personalised Multi-User Dashboards","Build applications that provide unique data to each logged-in user using personalised multi-user dashboards.","https:\u002F\u002Fdashboard.flowfuse.com\u002Fuser\u002Fmulti-tenancy.html",{"edge":514,"hub":514,"fleet":514},{"id":635,"title":636,"description":637,"changelog":638,"subfeature":514,"showOnPricing":551,"tiers":641},"dashboards-view","Dashboards View","Browse and open every dashboard across your team from a dedicated Dashboards view, at both team and application level, without leaving FlowFuse.",[639],{"url":640,"release":604},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":514,"hub":514,"fleet":514},{"id":643,"title":644,"description":645,"docsLink":646,"tiers":647},"blueprints-converge","Blueprints","Ready-made starting points for your apps, from cross-team Converge templates to OT and IT specific blueprints.","\u002Fdocs\u002Fuser\u002Fconcepts\u002F#blueprint",{"edge":514,"hub":514,"fleet":514},{"id":649,"title":650,"subfeature":514,"showOnPricing":551,"tiers":651},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":514,"hub":551,"fleet":514},{"id":653,"title":654,"subfeature":514,"showOnPricing":551,"tiers":655},"blueprints-it-apps","Blueprints - IT APPS",{"edge":551,"hub":514,"fleet":551},{"id":657,"title":658,"description":659,"changelog":660,"showOnPricing":551,"tiers":664},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[661],{"url":662,"release":663},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":514,"hub":514,"fleet":514},{"id":666,"title":667,"description":668,"changelog":669,"showOnPricing":551,"tiers":672},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[670],{"url":671,"release":561},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":514,"hub":514,"fleet":514},{"id":674,"title":675,"description":676,"changelog":677,"showOnPricing":551,"tiers":680},"embedded-editor-tab-title","Embedded Editor Browser Tab Title","The browser tab title updates to reflect the active Node-RED canvas tab when working in the embedded editor.",[678],{"url":679,"release":663},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":514,"hub":514,"fleet":514},{"id":682,"title":683,"features":684},"deploy","Deploy",[685,691,700,706,712,718,724,730,735],{"id":686,"title":687,"description":688,"docsLink":689,"tiers":690},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":514,"hub":514,"fleet":514},{"id":692,"title":693,"description":694,"docsLink":695,"changelog":696,"tiers":699},"edge-devices","Edge Instances","Deploy and mange your Node-RED instances on edge PLCs and gateways, with full visibility and control from the cloud.","\u002Fdocs\u002Fdevice-agent\u002Fintroduction\u002F",[697],{"url":698,"release":541},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":514,"hub":551,"fleet":514},{"id":701,"title":702,"description":703,"docsLink":704,"tiers":705},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":551,"hub":514,"fleet":551},{"id":707,"title":708,"description":709,"docsLink":710,"tiers":711},"mqtt-broker","MQTT Broker","Manage and create MQTT clients to transport data for efficient messaging and communication within your applications.","\u002Fdocs\u002Fuser\u002Fteambroker\u002F",{"edge":514,"hub":551,"fleet":514},{"id":713,"title":714,"description":715,"docsLink":716,"showOnPricing":551,"tiers":717},"project-nodes","Project Nodes aka seamless project comms","FlowFuse Project Nodes enable the passing of data and messages between your Node-RED projects.","\u002Fdocs\u002Fuser\u002Fprojectnodes\u002F",{"edge":514,"hub":514,"fleet":514},{"id":719,"title":720,"description":721,"docsLink":722,"tiers":723},"devops-pipelines","DevOps Pipelines","Set up different environments for development, testing, and production Node-RED instances to support a full software delivery lifecycle.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F",{"edge":514,"hub":514,"fleet":514},{"id":725,"title":726,"description":727,"docsLink":728,"tiers":729},"git-integration","Git Integration","Back up your flows to a remote Git repository through a DevOps Pipeline. Supports GitHub and Azure DevOps repositories.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F#git-repository-stage",{"edge":551,"hub":514,"fleet":551},{"id":731,"title":732,"description":733,"docsLink":728,"subfeature":514,"showOnPricing":551,"tiers":734},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":551,"hub":514,"fleet":551},{"id":736,"title":737,"description":738,"docsLink":728,"changelog":739,"subfeature":514,"showOnPricing":551,"tiers":742},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[740],{"url":741,"release":663},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":551,"hub":514,"fleet":551},{"id":744,"title":745,"features":746},"operate-maintain","Operate & Maintain",[747,753,759,764,772,776,780,785,791,797,802,808,812,816],{"id":748,"title":749,"description":750,"docsLink":751,"tiers":752},"snapshots","Snapshots & Version History","Automatic snapshots on remote devices and hosted instances, plus a full version history timeline so you can roll back to any prior state.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F",{"edge":514,"hub":514,"fleet":514},{"id":754,"title":755,"description":756,"docsLink":757,"subfeature":514,"showOnPricing":551,"tiers":758},"auto-snapshot-remote","Auto Snapshot (Remote)","Automatically capture a snapshot every time a remote instance is deployed, so you always have a recoverable history of what was running on each device.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#auto-snapshots",{"edge":514,"hub":514,"fleet":514},{"id":760,"title":761,"description":762,"docsLink":757,"subfeature":514,"showOnPricing":551,"tiers":763},"auto-snapshot-hosted","Auto Snapshot (Hosted)","Automatically capture a snapshot every time a hosted instance is deployed, so you always have a recoverable history of what was running.",{"edge":514,"hub":514,"fleet":514},{"id":765,"title":766,"description":767,"changelog":768,"subfeature":514,"showOnPricing":551,"tiers":771},"snapshot-comparison","Snapshot Comparison","Compare two snapshots side-by-side with a navigable diff view. Step through every changed, added, or deleted node and see property and code diffs.",[769],{"url":770,"release":663},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":514,"hub":514,"fleet":514},{"id":773,"title":774,"subfeature":514,"showOnPricing":551,"tiers":775},"version-history-timeline","Version History Timeline",{"edge":514,"hub":514,"fleet":514},{"id":777,"title":778,"tiers":779},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":514,"hub":514,"fleet":514},{"id":781,"title":782,"description":783,"tiers":784},"device-fleet-updates","Device Fleet Updates","Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes, securely without requiring full device access for your whole organisation.",{"edge":514,"hub":551,"fleet":514},{"id":786,"title":787,"description":788,"docsLink":789,"tiers":790},"device-group-management","Device Group Management","Logically group devices assigned to an application and integrate device groups into your DevOps Pipeline for coordinated fleet updates.","\u002Fdocs\u002Fuser\u002Fdevice-groups\u002F",{"edge":514,"hub":551,"fleet":514},{"id":792,"title":793,"description":794,"docsLink":795,"tiers":796},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":551,"hub":514,"fleet":551},{"id":798,"title":799,"description":800,"tiers":801},"performance-monitoring","Performance Monitoring & Alerts","Track CPU, memory, and event loop performance across your instances and devices, with email alerts when something needs your attention.",{"edge":514,"hub":514,"fleet":514},{"id":803,"title":804,"description":805,"docsLink":806,"subfeature":514,"showOnPricing":551,"tiers":807},"instance-monitoring","Instance Monitoring","Enable alerts to be sent via email when your Node-RED instances encounter issues.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#alerts",{"edge":514,"hub":514,"fleet":514},{"id":809,"title":810,"subfeature":514,"showOnPricing":551,"tiers":811},"email-alerts","Email Alerts",{"edge":514,"hub":514,"fleet":514},{"id":813,"title":814,"showOnPricing":551,"tiers":815},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":514,"hub":514,"fleet":514},{"id":817,"title":818,"tiers":819},"protected-instances","Protected Instances",{"edge":551,"hub":514,"fleet":551},{"id":821,"title":822,"features":823},"govern-secure","Govern and Secure",[824,833,839,845,850,856,862,868,876,882,888,894],{"id":825,"title":826,"description":827,"docsLink":828,"changelog":829,"tiers":832},"single-sign-on","Single Sign-On (SSO)","Configure FlowFuse to work with your own SSO provider, allowing users to access FlowFuse with a single set of login credentials.","\u002Fdocs\u002Fadmin\u002Fsso\u002F",[830],{"url":831,"release":604},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":514,"hub":514,"fleet":514},{"id":834,"title":835,"description":836,"docsLink":837,"tiers":838},"two-factor-authentication","Two-Factor Authentication","Two-factor authentication adds an extra layer of security to your FlowFuse account.","\u002Fdocs\u002Fuser\u002Fuser-settings\u002F#two-factor-authentication",{"edge":514,"hub":514,"fleet":514},{"id":840,"title":841,"description":842,"docsLink":843,"tiers":844},"certified-nodes-it","Certified Nodes - IT","IT certified node bundle includes: Redis, MQTT, HTTP Request, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server","\u002Fblog\u002F2025\u002F07\u002Fcertified-nodes-v2\u002F",{"edge":551,"hub":514,"fleet":514},{"id":846,"title":847,"description":848,"tiers":849},"certified-nodes-ot","Certified OT Connections - OPC-UA, Modbus, etc.","OT certified node bundle includes: OPC-UA, Modbus TCP & RTU, RTSP, EtherNet\u002FIP, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server",{"edge":514,"hub":551,"fleet":551},{"id":851,"title":852,"description":853,"docsLink":854,"tiers":855},"audit-log","Audit Log","Keep track of everything going on in your Node-RED instances and FlowFuse. Audit Logs provide details on what actions have taken place, when they happened, and who did them.","\u002Fdocs\u002Fuser\u002Flogs\u002F#audit-log",{"edge":514,"hub":514,"fleet":514},{"id":857,"title":858,"description":859,"docsLink":860,"tiers":861},"role-based-access-control","Role-Based Access Control","Control who can do what at both the team and application level, from viewers to admins.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F",{"edge":514,"hub":514,"fleet":514},{"id":863,"title":864,"description":865,"docsLink":866,"subfeature":514,"showOnPricing":551,"tiers":867},"application-level-rbac","Application-Level RBAC","Fine-grained access control per application, allowing team members to have different permission levels across different applications without requiring separate teams.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F#application-level-rbac",{"edge":514,"hub":514,"fleet":514},{"id":869,"title":870,"description":871,"changelog":872,"subfeature":514,"showOnPricing":551,"tiers":875},"scoped-personal-access-tokens","Scoped Personal Access Tokens","Restrict a Personal Access Token to specific teams, limit it to read-only operations, or control whether it carries admin privileges.",[873],{"url":874,"release":604},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":514,"hub":514,"fleet":514},{"id":877,"title":878,"description":879,"docsLink":880,"showOnPricing":551,"tiers":881},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":514,"hub":514,"fleet":514},{"id":883,"title":884,"description":885,"docsLink":886,"showOnPricing":551,"tiers":887},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":514,"hub":514,"fleet":514},{"id":889,"title":890,"description":891,"docsLink":892,"tiers":893},"baa-for-hipaa","BAA for HIPAA","FlowFuse can sign a Business Associate Agreement to ensure proper safeguarding of protected health information handled on your behalf.","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.5\u002F",{"edge":551,"hub":514,"fleet":551},{"id":895,"title":896,"description":897,"tiers":898},"sbom","Software Bill of Materials","A complete list of all software components used in your Node-RED instances and hosted applications, including version numbers and license information.",{"edge":551,"hub":514,"fleet":551},{"id":900,"title":901,"features":902},"support","Support",[903,908,912],{"id":904,"title":905,"docsLink":906,"tiers":907},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":514,"hub":514,"fleet":514},{"id":909,"title":910,"showOnPricing":551,"tiers":911},"live-chat-support","Live Chat Support",{"edge":514,"hub":514,"fleet":514},{"id":913,"title":914,"docsLink":915,"tiers":916},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":514,"hub":514,"fleet":514},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[920,923,926,929,932,935,937,940,943,946,949,951,954,957,960,963,966,969,972,975,978,981,984,987,990,993,996,999,1002,1005,1008,1011,1014,1017,1020,1023,1026,1029,1032,1035,1038,1041,1044,1047,1050,1053,1056,1059,1062,1064,1067,1070,1073,1076,1079,1082,1085,1087,1090,1093,1096,1099,1102,1104,1107,1110,1113,1116,1119,1122,1125,1128,1131,1134,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1180,1183,1186,1189,1192,1195,1198,1201,1204,1207,1210,1213,1216,1219,1222,1225,1228,1231,1234,1236,1239,1242,1245,1248,1251,1254,1257,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450],{"path":921,"title":922},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":924,"title":925},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":927,"title":928},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":930,"title":931},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":933,"title":934},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":936,"title":644},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":938,"title":939},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":941,"title":942},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":944,"title":945},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":947,"title":948},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":950,"title":835},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":952,"title":953},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":955,"title":956},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":958,"title":959},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":961,"title":962},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":964,"title":965},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":967,"title":968},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":970,"title":971},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":973,"title":974},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":976,"title":977},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":979,"title":980},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":982,"title":983},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":985,"title":986},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":988,"title":989},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":991,"title":992},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":994,"title":995},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":997,"title":998},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":1000,"title":1001},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":1003,"title":1004},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":1006,"title":1007},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":1009,"title":1010},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":1012,"title":1013},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":1015,"title":1016},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":1018,"title":1019},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":1021,"title":1022},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":1024,"title":1025},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":1027,"title":1028},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":1030,"title":1031},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":1033,"title":1034},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":1036,"title":1037},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":1039,"title":1040},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":1042,"title":1043},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":1045,"title":1046},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1048,"title":1049},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1051,"title":1052},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1054,"title":1055},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1057,"title":1058},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1060,"title":1061},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1063,"title":1061},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1065,"title":1066},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1068,"title":1069},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1071,"title":1072},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1074,"title":1075},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1077,"title":1078},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1080,"title":1081},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1083,"title":1084},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1086,"title":1084},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1088,"title":1089},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1091,"title":1092},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1094,"title":1095},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1097,"title":1098},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1100,"title":1101},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1103,"title":1101},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1105,"title":1106},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1108,"title":1109},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1111,"title":1112},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1114,"title":1115},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1117,"title":1118},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1120,"title":1121},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1123,"title":1124},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1126,"title":1127},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1129,"title":1130},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1132,"title":1133},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1135,"title":774},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1137,"title":1138},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1140,"title":1141},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1143,"title":1144},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1146,"title":1147},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1149,"title":1150},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1152,"title":1153},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1155,"title":1156},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1158,"title":1159},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1161,"title":1162},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1164,"title":1165},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1167,"title":1168},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1170,"title":1171},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1173,"title":1174},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1176,"title":1177},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1179,"title":774},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1181,"title":1182},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1184,"title":1185},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1187,"title":1188},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1190,"title":1191},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1193,"title":1194},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1196,"title":1197},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1199,"title":1200},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1202,"title":1203},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1205,"title":1206},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1208,"title":1209},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1211,"title":1212},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1214,"title":1215},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1217,"title":1218},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1220,"title":1221},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1223,"title":1224},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1226,"title":1227},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1229,"title":1230},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1232,"title":1233},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1235,"title":1233},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1237,"title":1238},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1240,"title":1241},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1243,"title":1244},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1246,"title":1247},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1249,"title":1250},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1252,"title":1253},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1255,"title":1256},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1258,"title":598},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1260,"title":1261},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1263,"title":1264},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1266,"title":1267},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1269,"title":1270},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1272,"title":1273},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1275,"title":1276},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1278,"title":1279},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1281,"title":1282},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1284,"title":1285},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1287,"title":1288},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1290,"title":1291},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1293,"title":1294},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1296,"title":1297},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1299,"title":1300},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1302,"title":1303},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1305,"title":1306},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1308,"title":1309},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1311,"title":1312},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1314,"title":1315},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1317,"title":1318},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1320,"title":1321},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1323,"title":1324},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1326,"title":1327},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1329,"title":1330},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1332,"title":1333},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1335,"title":1336},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1338,"title":1339},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1341,"title":1342},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1344,"title":1345},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1347,"title":1348},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1350,"title":1351},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1353,"title":1354},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1356,"title":1357},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1359,"title":1360},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1362,"title":1363},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1365,"title":1366},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1368,"title":1369},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1371,"title":1372},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1374,"title":1375},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1377,"title":1378},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1380,"title":1381},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1383,"title":1384},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1386,"title":1387},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1389,"title":1390},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1392,"title":1393},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1395,"title":1396},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1398,"title":1399},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1401,"title":1402},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1404,"title":1405},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1407,"title":1408},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1410,"title":667},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1412,"title":1413},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1415,"title":1416},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1418,"title":1419},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1421,"title":1422},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1424,"title":1425},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1427,"title":1428},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1430,"title":1431},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1433,"title":1434},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1436,"title":1437},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1439,"title":1440},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1442,"title":1443},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1445,"title":1446},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1448,"title":1449},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1451,"title":1452},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105897352]