[{"data":1,"prerenderedAt":2293},["ShallowReactive",2],{"blog-\u002Fblog\u002F2025\u002F11\u002Fstore-and-forward-edge-data-buffering":3,"featureCatalog":1363,"changelog-titles":1758,"blog-all-for-related":2292},{"id":4,"title":5,"authors":6,"body":8,"cta":1341,"date":1342,"description":1343,"extension":1344,"features":1341,"image":1345,"lastUpdated":1346,"meta":1347,"navigation":77,"path":1353,"release":1341,"seo":1354,"sitemap":1355,"stem":1356,"subtitle":1357,"tags":1358,"tldr":1361,"video":1341,"__hash__":1362},"blog\u002Fblog\u002F2025\u002F11\u002Fstore-and-forward-edge-data-buffering.md","Store-and-Forward at the Edge: Buffering Production Data During Network Outages",[7],"sumit-shinde",{"type":9,"value":10,"toc":1322},"minimark",[11,15,18,21,24,31,36,39,42,208,211,215,218,221,226,229,252,256,259,262,265,274,278,281,284,308,318,327,369,376,392,395,399,402,426,435,443,497,505,524,539,547,554,558,561,564,585,593,626,634,640,649,680,688,712,720,744,752,760,763,767,770,775,799,824,869,877,898,906,919,922,926,929,933,959,967,981,989,1006,1014,1030,1050,1055,1059,1067,1074,1106,1114,1130,1150,1163,1183,1190,1193,1220,1228,1288,1292,1295,1298,1301,1304,1311,1318],[12,13,14],"p",{},"Network outages happen. A fiber cut, a switch failure, or infrastructure maintenance can take your connectivity offline without warning. When it does, your PLCs continue operating normally, they don't wait for the network to recover.",[12,16,17],{},"The problem is that all the data they generate during that outage has nowhere to go. Production metrics, quality measurements, and alarm events accumulate with no path to your historian or cloud platform. When connectivity returns, you're left with gaps in your operational records. Those gaps create real problems: incomplete batch records for quality audits, missing data for troubleshooting production issues, and compliance documentation that doesn't hold up under review.",[12,19,20],{},"Store-and-forward solves this. This article walks through building a store-and-forward system with FlowFuse that maintains complete data continuity during network failures.",[12,22,23],{},"Below is the demo video where I show how production data can be lost without buffering, and how buffering prevents that from happening.",[25,26],"lite-youtube",{"videoid":27,"params":28,"style":29,"title":30},"J1gDj6S-ijI","rel=0","margin-top: 20px; margin-bottom: 20px; width: 100%; height: 480px;","YouTube video player",[32,33,35],"h2",{"id":34},"what-is-store-and-forward","What is Store-and-Forward?",[12,37,38],{},"Store-and-forward is a pattern where data is saved locally before transmission, then forwarded when network connectivity is available. Your edge device writes every data point to local SQLite storage first. If the network is up, the data transmits to your destination, MQTT broker, historian, cloud platform, or database. If the network is down, the data stays in storage until connectivity returns.",[12,40,41],{},"The edge device operates in three states. During normal operation, data writes to the buffer and forwards successfully, the buffer stays near-empty. During a network outage, data continues writing to the buffer but cannot forward, the buffer grows. When connectivity returns, the device forwards the buffered backlog in chronological order while continuing to collect new data, the buffer drains back to empty.",[43,44,49],"pre",{"className":45,"code":46,"language":47,"meta":48,"style":48},"language-mermaid shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","flowchart TD\n    Source[PLC \u002F Sensor]\n    Destination[Cloud \u002F Broker \u002F Server]\n\n    Source --> Start[Data Arrives at Edge]\n    Start --> Save[Store in Local Buffer]\n    Save --> Check{Network Available?}\n\n    Check -->|Connected| Send[Send Data]\n    Send --> Destination\n    Destination --> Clear[Remove Data from Buffer]\n\n    Check -->|Disconnected| Wait[Keep Data in Buffer]\n    Wait --> Retry[Retry Until Network Restored]\n    Retry --> Check\n\n    %% Styling (consistent theme)\n    style Source fill:#3B82F6,color:#fff\n    style Start fill:#3B82F6,color:#fff\n    style Save fill:#818CF8,color:#fff\n    style Check fill:#6366F1,color:#fff\n    style Send fill:#60A5FA,color:#fff\n    style Destination fill:#60A5FA,color:#fff\n    style Clear fill:#93C5FD,color:#000\n    style Wait fill:#A5B4FC,color:#fff\n    style Retry fill:#BFDBFE,color:#000\n","mermaid","",[50,51,52,60,66,72,79,85,91,97,102,108,114,120,125,131,137,143,148,154,160,166,172,178,184,190,196,202],"code",{"__ignoreMap":48},[53,54,57],"span",{"class":55,"line":56},"line",1,[53,58,59],{},"flowchart TD\n",[53,61,63],{"class":55,"line":62},2,[53,64,65],{},"    Source[PLC \u002F Sensor]\n",[53,67,69],{"class":55,"line":68},3,[53,70,71],{},"    Destination[Cloud \u002F Broker \u002F Server]\n",[53,73,75],{"class":55,"line":74},4,[53,76,78],{"emptyLinePlaceholder":77},true,"\n",[53,80,82],{"class":55,"line":81},5,[53,83,84],{},"    Source --> Start[Data Arrives at Edge]\n",[53,86,88],{"class":55,"line":87},6,[53,89,90],{},"    Start --> Save[Store in Local Buffer]\n",[53,92,94],{"class":55,"line":93},7,[53,95,96],{},"    Save --> Check{Network Available?}\n",[53,98,100],{"class":55,"line":99},8,[53,101,78],{"emptyLinePlaceholder":77},[53,103,105],{"class":55,"line":104},9,[53,106,107],{},"    Check -->|Connected| Send[Send Data]\n",[53,109,111],{"class":55,"line":110},10,[53,112,113],{},"    Send --> Destination\n",[53,115,117],{"class":55,"line":116},11,[53,118,119],{},"    Destination --> Clear[Remove Data from Buffer]\n",[53,121,123],{"class":55,"line":122},12,[53,124,78],{"emptyLinePlaceholder":77},[53,126,128],{"class":55,"line":127},13,[53,129,130],{},"    Check -->|Disconnected| Wait[Keep Data in Buffer]\n",[53,132,134],{"class":55,"line":133},14,[53,135,136],{},"    Wait --> Retry[Retry Until Network Restored]\n",[53,138,140],{"class":55,"line":139},15,[53,141,142],{},"    Retry --> Check\n",[53,144,146],{"class":55,"line":145},16,[53,147,78],{"emptyLinePlaceholder":77},[53,149,151],{"class":55,"line":150},17,[53,152,153],{},"    %% Styling (consistent theme)\n",[53,155,157],{"class":55,"line":156},18,[53,158,159],{},"    style Source fill:#3B82F6,color:#fff\n",[53,161,163],{"class":55,"line":162},19,[53,164,165],{},"    style Start fill:#3B82F6,color:#fff\n",[53,167,169],{"class":55,"line":168},20,[53,170,171],{},"    style Save fill:#818CF8,color:#fff\n",[53,173,175],{"class":55,"line":174},21,[53,176,177],{},"    style Check fill:#6366F1,color:#fff\n",[53,179,181],{"class":55,"line":180},22,[53,182,183],{},"    style Send fill:#60A5FA,color:#fff\n",[53,185,187],{"class":55,"line":186},23,[53,188,189],{},"    style Destination fill:#60A5FA,color:#fff\n",[53,191,193],{"class":55,"line":192},24,[53,194,195],{},"    style Clear fill:#93C5FD,color:#000\n",[53,197,199],{"class":55,"line":198},25,[53,200,201],{},"    style Wait fill:#A5B4FC,color:#fff\n",[53,203,205],{"class":55,"line":204},26,[53,206,207],{},"    style Retry fill:#BFDBFE,color:#000\n",[12,209,210],{},"This solves the core problem in industrial data collection: network failures creating gaps in your time-series data. A four-hour outage would normally mean four hours of missing production data. With store-and-forward, that same outage causes zero data loss. Your destination system receives complete chronological data with only a delivery delay.",[32,212,214],{"id":213},"getting-started","Getting Started",[12,216,217],{},"Let's build a store-and-forward system to protect your data during network outages.",[12,219,220],{},"We'll approach this in six steps: establish a connection to collect data, set up a local buffer to temporarily store that data, write incoming data to the buffer, monitor network connectivity status, create forwarding logic to transmit buffered data when connectivity returns, and finally add error handling and buffer management to ensure reliable operation.",[222,223,225],"h3",{"id":224},"prerequisites","Prerequisites",[12,227,228],{},"You'll need the following before implementing store-and-forward:",[230,231,232,240,246],"ul",{},[233,234,235,239],"li",{},[236,237,238],"strong",{},"Edge Device Running FlowFuse Agent",": A running FlowFuse instance deployed on your edge hardware or gateway device.",[233,241,242,245],{},[236,243,244],{},"node-red-node-sqlite",": SQLite node for local data storage.",[233,247,248,251],{},[236,249,250],{},"node-red-contrib-ping",": Ping node for connectivity monitoring.",[222,253,255],{"id":254},"step-1-set-up-data-collection","Step 1: Set Up Data Collection",[12,257,258],{},"Data collection is the foundation of store-and-forward. Your edge device needs reliable connectivity to your data sources before you can buffer and forward their data.",[12,260,261],{},"FlowFuse handles this through Node-RED's 5,000+ community nodes, which support virtually every industrial protocol and interface, Modbus, OPC UA, MQTT, Ethernet\u002FIP, GPIO pins, serial connections, and more. You collect data from your sources, transform it into the format you need, and prepare it for buffering.",[12,263,264],{},"For this guide, we'll assume you already have data flowing into FlowFuse. The store-and-forward pattern works the same regardless of which data sources or protocols you're using.",[12,266,267,268,273],{},"For more information on how FlowFuse can help you connect, collect, transform, and contextualize your data, and how it simplifies deployment, management, scaling, and security with enterprise features for production environments, ",[269,270,272],"a",{"href":271},"\u002Fbook-demo\u002F","book a demo",".",[222,275,277],{"id":276},"step-2-implement-sqlite-buffering","Step 2: Implement SQLite Buffering",[12,279,280],{},"SQLite provides the persistent storage layer for your store-and-forward buffer. It's lightweight, requires no separate database server, and handles the write volumes typical of industrial data collection without issue.",[12,282,283],{},"Follow these steps to set up your SQLite buffer:",[285,286,287,294],"ol",{},[233,288,289,290,293],{},"Drag the ",[236,291,292],{},"sqlite"," node from the palette onto your workspace.",[233,295,296,297,299,300,303,304,307],{},"Double-click the node to open its configuration panel. Click the pencil icon next to the Database field to create a new database configuration. Give it a name like ",[236,298,292],{},", select ",[236,301,302],{},"Read-write-create"," as the mode, and click ",[236,305,306],{},"Add"," to save the configuration.",[12,309,310,315],{},[311,312],"img",{"alt":313,"dataZoomable":48,"src":314},"SQLite database configuration with read-write-create mode enabled","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fsqlite-config.png",[316,317,313],"em",{},[285,319,320],{"start":68},[233,321,322,323,326],{},"Set the SQL Query mode to ",[236,324,325],{},"Fixed Statement",". In the SQL Query field, enter:",[43,328,332],{"className":329,"code":330,"language":331,"meta":48,"style":48},"language-sql shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","CREATE TABLE IF NOT EXISTS data_buffer (\n    id INTEGER PRIMARY KEY AUTOINCREMENT,\n    timestamp INTEGER NOT NULL,\n    sent INTEGER DEFAULT 0,\n    payload TEXT,\n    created_at INTEGER DEFAULT (strftime('%s','now') * 1000)\n);\n","sql",[50,333,334,339,344,349,354,359,364],{"__ignoreMap":48},[53,335,336],{"class":55,"line":56},[53,337,338],{},"CREATE TABLE IF NOT EXISTS data_buffer (\n",[53,340,341],{"class":55,"line":62},[53,342,343],{},"    id INTEGER PRIMARY KEY AUTOINCREMENT,\n",[53,345,346],{"class":55,"line":68},[53,347,348],{},"    timestamp INTEGER NOT NULL,\n",[53,350,351],{"class":55,"line":74},[53,352,353],{},"    sent INTEGER DEFAULT 0,\n",[53,355,356],{"class":55,"line":81},[53,357,358],{},"    payload TEXT,\n",[53,360,361],{"class":55,"line":87},[53,362,363],{},"    created_at INTEGER DEFAULT (strftime('%s','now') * 1000)\n",[53,365,366],{"class":55,"line":93},[53,367,368],{},");\n",[12,370,371,372,375],{},"The payload stores the serialized data as JSON. The ",[50,373,374],{},"sent"," flag indicates whether the record is still pending (0) or has been successfully delivered (1), this acts as a safety marker to prevent cleanup of unsent data.",[285,377,378,389],{},[233,379,380,381,384,385,388],{},"Connect an ",[236,382,383],{},"Inject"," node to ",[236,386,387],{},"Sqlite"," node",[233,390,391],{},"Deploy your flow and click the inject node button to create the table.",[12,393,394],{},"Your SQLite buffer is now ready to store data during network outages. The next step implements the logic to write incoming data to this buffer.",[222,396,398],{"id":397},"step-3-store-incoming-data-in-buffer","Step 3: Store Incoming Data in Buffer",[12,400,401],{},"With your SQLite buffer ready, implement the logic to write incoming PLC data to storage.",[285,403,404,411],{},[233,405,406,407,410],{},"Drag a ",[236,408,409],{},"JSON"," node onto the canvas and connect it to your data input source.",[233,412,413,414,417,418,421,422,425],{},"Double-click the node to open its configuration. Set the Action to ",[50,415,416],{},"Always convert to JSON String"," and set the Property to ",[50,419,420],{},"msg.payload",", then click ",[236,423,424],{},"Done"," to save.",[427,428,429],"blockquote",{},[12,430,431,434],{},[236,432,433],{},"Note",": JSON converts your data object into a text string for storage. If your data source already provides a JSON string (not an object), you must delete this node.",[12,436,437,441],{},[311,438],{"alt":439,"dataZoomable":48,"src":440},"JSON node configured to stringify payload data for storage","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fstringify-json.png",[316,442,439],{},[285,444,445,454],{"start":68},[233,446,406,447,450,451,453],{},[236,448,449],{},"Change"," node onto the canvas and connect it to the ",[236,452,409],{}," node.",[233,455,456,457,459,460],{},"Double-click the ",[236,458,449],{}," node to configure it. Add the following rules:",[230,461,462,476,487],{},[233,463,464,467,468,471,472,475],{},[236,465,466],{},"Rule 1",": Set ",[50,469,470],{},"msg.params"," to ",[50,473,474],{},"{}"," (JSONata expression)",[233,477,478,467,481,471,484],{},[236,479,480],{},"Rule 2",[50,482,483],{},"msg.params.$ts",[50,485,486],{},"msg.timestamp",[233,488,489,467,492,471,495],{},[236,490,491],{},"Rule 3",[50,493,494],{},"msg.params.$payload",[50,496,420],{},[12,498,499,503],{},[311,500],{"alt":501,"dataZoomable":48,"src":502},"Change node rules for preparing SQLite insert parameters","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fset-params-step-3.png",[316,504,501],{},[285,506,507,514],{"start":81},[233,508,509,510,450,512,453],{},"Drag another ",[236,511,387],{},[236,513,449],{},[233,515,516,517,519,520,523],{},"Double-click the node to configure it. Select your existing ",[236,518,387],{}," database, set the SQL Query mode to ",[50,521,522],{},"Prepared Statement",", and in the SQL Query field, enter:",[43,525,527],{"className":329,"code":526,"language":331,"meta":48,"style":48},"INSERT INTO data_buffer (timestamp, payload, sent)\nVALUES ($ts, $payload, 0);\n",[50,528,529,534],{"__ignoreMap":48},[53,530,531],{"class":55,"line":56},[53,532,533],{},"INSERT INTO data_buffer (timestamp, payload, sent)\n",[53,535,536],{"class":55,"line":62},[53,537,538],{},"VALUES ($ts, $payload, 0);\n",[285,540,541],{"start":93},[233,542,543,544,546],{},"Click ",[236,545,424],{}," to save the configuration and deploy your flow.",[12,548,549,550,553],{},"Your buffer now accumulates all incoming data. Each data point is serialized to JSON, structured into parameters, and written to SQLite with ",[50,551,552],{},"sent=0"," (not yet forwarded). The prepared statement approach prevents SQL injection issues and handles special characters correctly.",[222,555,557],{"id":556},"step-4-monitor-network-connectivity","Step 4: Monitor Network Connectivity",[12,559,560],{},"Network connectivity monitoring determines when your system can forward buffered data. The ping node checks connectivity to your destination system, and when the network is available, it triggers the forwarding process.",[12,562,563],{},"Follow these steps to implement connectivity monitoring:",[285,565,566,572],{},[233,567,406,568,571],{},[236,569,570],{},"Ping"," node onto the canvas.",[233,573,574,575,578,579,582,583,425],{},"Double-click the node to configure it. Enter the IP address or hostname of your destination system in the Target field (e.g., ",[50,576,577],{},"broker.flowfuse.cloud","), select mode to \"Automatic\", set \"Ping every\" to ",[50,580,581],{},"30"," seconds (adjust based on your requirements), name it \"Network Health Check\", and click ",[236,584,424],{},[12,586,587,591],{},[311,588],{"alt":589,"dataZoomable":48,"src":590},"Ping node configured to monitor network connectivity every 30 seconds","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fping.png",[316,592,589],{},[285,594,595,602],{"start":68},[233,596,406,597,450,600,453],{},[236,598,599],{},"Switch",[236,601,570],{},[233,603,456,604,606,607,609,610],{},[236,605,599],{}," node to configure it. Set the Property to ",[50,608,420],{},",",[230,611,612,619],{},[233,613,614,615,618],{},"add Rule 1 as ",[50,616,617],{},"false"," (network is down),",[233,620,621,622,625],{},"add Rule 2 as ",[50,623,624],{},"otherwise"," (network is reachable).",[12,627,628,632],{},[311,629],{"alt":630,"dataZoomable":48,"src":631},"Switch node routing messages based on network connectivity status","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fif-connected-to-internet.png",[316,633,630],{},[285,635,636],{"start":81},[233,637,543,638,425],{},[236,639,424],{},[12,641,642,643,645,646,648],{},"The switch node routes messages based on ping results. When ping fails, ",[50,644,420],{}," is ",[50,647,617],{},". Otherwise, the ping succeeded with a response time.",[285,650,651,658],{"start":87},[233,652,653,654,657],{},"Drag two ",[236,655,656],{},"change"," nodes onto the canvas. Connect the first one to output 1 of the switch node (network down), and the second one to output 2 (network reachable).",[233,659,660,661],{},"Double-click the first change node to configure it:",[230,662,663,673,676],{},[233,664,665,467,667,471,670,672],{},[236,666,466],{},[50,668,669],{},"flow.networkOnline",[50,671,617],{}," (boolean) ( make sure it is stored in the persistent storage )",[233,674,675],{},"Name it \"Set Network Offline\"",[233,677,543,678,425],{},[236,679,424],{},[12,681,682,686],{},[311,683],{"alt":684,"dataZoomable":48,"src":685},"Change node setting network offline flag in persistent storage","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fset-network-offline.png",[316,687,684],{},[285,689,690],{"start":99},[233,691,692,693],{},"Double-click the second change node to configure it:\n",[230,694,695,705,708],{},[233,696,697,467,699,471,701,704],{},[236,698,466],{},[50,700,669],{},[50,702,703],{},"true"," (boolean)",[233,706,707],{},"Name it \"Set Network Online\"",[233,709,543,710,425],{},[236,711,424],{},[12,713,714,718],{},[311,715],{"alt":716,"dataZoomable":48,"src":717},"Change node setting network online flag when connectivity is restored","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fset-network-online.png",[316,719,716],{},[285,721,722],{"start":104},[233,723,509,724,726,727],{},[236,725,656],{}," node onto the canvas and configure it:\n",[230,728,729],{},[233,730,731,467,733,471,736,738,739,743],{},[236,732,466],{},[50,734,735],{},"flow.flowError",[236,737,617],{}," (this resets the error state triggered in the ",[269,740,742],{"href":741},"#handle-errors-and-disconnections","Handle Errors and Disconnections"," section).",[12,745,746,750],{},[311,747],{"alt":748,"dataZoomable":48,"src":749},"Change node resetting error state when network becomes available","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fflow-error.png",[316,751,748],{},[285,753,754],{"start":110},[233,755,406,756,759],{},[236,757,758],{},"Link Out"," node onto the canvas and connect it to the \"Set Network Online\" node. Name it \"Trigger Forward\".",[12,761,762],{},"Your connectivity monitoring is now complete. When the network is available, the system will trigger the forwarding logic to send buffered data.",[222,764,766],{"id":765},"step-5-build-the-forwarding-logic","Step 5: Build the Forwarding Logic",[12,768,769],{},"The forwarding logic retrieves unsent data from the buffer, prepares it for transmission, and sends it to the destination. This section shows how to build a forwarding system that processes buffered data in batches.",[771,772,774],"h4",{"id":773},"retrieve-and-prepare-unsent-records","Retrieve and Prepare Unsent Records",[285,776,777,786],{},[233,778,406,779,782,783,785],{},[236,780,781],{},"Link In"," node onto the canvas and name it \"Trigger Forward\". Link this to the ",[236,784,758],{}," node from Step 4.",[233,787,788,789,450,792,794,795,798],{},"Drag an ",[236,790,791],{},"SQLite",[236,793,781],{}," node. Name it \"Get Unsent Data\" and configure it by selecting your database, setting SQL Query mode to ",[236,796,797],{},"Fixed statement",", and entering the following SQL:",[43,800,802],{"className":329,"code":801,"language":331,"meta":48,"style":48},"   SELECT * FROM data_buffer \n   WHERE sent = 0 \n   ORDER BY timestamp ASC \n   LIMIT 50;\n",[50,803,804,809,814,819],{"__ignoreMap":48},[53,805,806],{"class":55,"line":56},[53,807,808],{},"   SELECT * FROM data_buffer \n",[53,810,811],{"class":55,"line":62},[53,812,813],{},"   WHERE sent = 0 \n",[53,815,816],{"class":55,"line":68},[53,817,818],{},"   ORDER BY timestamp ASC \n",[53,820,821],{"class":55,"line":74},[53,822,823],{},"   LIMIT 50;\n",[285,825,826,830,841],{"start":68},[233,827,543,828,425],{},[236,829,424],{},[233,831,406,832,835,836,838,839,273],{},[236,833,834],{},"Split"," node onto the canvas and connect it to the SQLite node. Configure it to split ",[236,837,420],{}," and click ",[236,840,424],{},[233,842,406,843,450,845,847,848],{},[236,844,449],{},[236,846,834],{}," node. Name it \"Prepare Forward Message\" and add the following rules:",[230,849,850,860],{},[233,851,852,467,854,471,857],{},[236,853,466],{},[50,855,856],{},"msg.record_id",[50,858,859],{},"msg.payload.id",[233,861,862,467,864,471,866],{},[236,863,480],{},[50,865,420],{},[50,867,868],{},"msg.payload.payload",[12,870,871,875],{},[311,872],{"alt":873,"dataZoomable":48,"src":874},"Change node extracting record ID and payload for forwarding","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fprepare-forward-msg.png",[316,876,873],{},[285,878,879,883],{"start":87},[233,880,543,881,425],{},[236,882,424],{},[233,884,406,885,450,887,889,890,893,894,421,896,273],{},[236,886,409],{},[236,888,449],{}," node. Configure it by setting Action to ",[236,891,892],{},"Always Convert to JSON Object"," and Property to ",[50,895,420],{},[236,897,424],{},[12,899,900,904],{},[311,901],{"alt":902,"dataZoomable":48,"src":903},"JSON node configured to parse stored JSON string back to object","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fparse-json.png",[316,905,902],{},[285,907,908,912],{"start":99},[233,909,543,910,425],{},[236,911,424],{},[233,913,406,914,450,916,918],{},[236,915,758],{},[236,917,409],{}," node. Name it \"Send to Destination\".",[12,920,921],{},"Your forwarding logic now retrieves unsent records, prepares them for transmission, and passes them to the next stage for sending.",[222,923,925],{"id":924},"step-6-send-data-and-handle-errors","Step 6: Send Data and Handle Errors",[12,927,928],{},"This step implements data transmission to your destination with comprehensive error handling and buffer management.",[771,930,932],{"id":931},"send-data-to-destination","Send Data to Destination",[285,934,935,943],{},[233,936,406,937,939,940,942],{},[236,938,781],{}," node onto the canvas and link it to the ",[236,941,758],{}," node from Step 5. Name it \"Send to Destination\".",[233,944,406,945,450,947,949,950,952,953,956,957,425],{},[236,946,599],{},[236,948,781],{}," node. Name it \"Check Network Online\", set the Property to ",[50,951,669],{},", add a condition ",[50,954,955],{},"is true",", and click ",[236,958,424],{},[12,960,961,965],{},[311,962],{"alt":963,"dataZoomable":48,"src":964},"Switch node verifying network connectivity before sending data","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fis-network-online.png",[316,966,963],{},[285,968,969],{"start":68},[233,970,509,971,973,974,952,976,956,979,425],{},[236,972,599],{}," node onto the canvas and connect it to the first switch node's output. Name it \"Check Flow Error\", set the Property to ",[50,975,735],{},[50,977,978],{},"is false",[236,980,424],{},[12,982,983,987],{},[311,984],{"alt":985,"dataZoomable":48,"src":986},"Switch node checking for error-free state before transmission","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fif-no-error.png",[316,988,985],{},[285,990,991],{"start":74},[233,992,406,993,995,996],{},[236,994,449],{}," node onto the canvas and connect it to the second switch node's output. Configure it to append the record ID into the payload for transmission confirmation:\n",[230,997,998],{},[233,999,1000,1001,471,1003],{},"Rule 1: Set ",[50,1002,856],{},[50,1004,1005],{},"msg.payload.record_id",[12,1007,1008,1012],{},[311,1009],{"alt":1010,"dataZoomable":48,"src":1011},"Change node preserving record ID for transmission confirmation","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fadd-record-id-to-payload.png",[316,1013,1010],{},[285,1015,1016],{"start":81},[233,1017,406,1018,450,1021,1023,1024,1027,1028,307],{},[236,1019,1020],{},"Project Out",[236,1022,449],{}," node. Double-click the node to open its configuration. Select \"Send to specified node\" as the mode, then enter select target \"broadcast message\" and enter topic (for example: ",[50,1025,1026],{},"acme_manufacturing\u002Fplant_01\u002Ffloor_2\u002Fcell_a\u002Fmachine_A12\u002Fmeasurements","). Click ",[236,1029,424],{},[427,1031,1032],{},[12,1033,1034,1037,1038,1041,1042,1045,1046,1049],{},[236,1035,1036],{},"Note:"," you can use any output node that suits your architecture instead of Project Out, such as ",[236,1039,1040],{},"MQTT Out"," for publishing to MQTT brokers, ",[236,1043,1044],{},"HTTP Request"," for sending data to REST APIs, ",[236,1047,1048],{},"Database"," nodes for writing directly to databases or other protocol-specific nodes depending on your destination requirements.",[285,1051,1052],{"start":87},[233,1053,1054],{},"Deploy the flow.",[771,1056,1058],{"id":1057},"mark-records-as-sent-and-clear-buffer","Mark Records as Sent and Clear Buffer",[285,1060,1061],{},[233,1062,406,1063,1066],{},[236,1064,1065],{},"Project In"," node onto the canvas, double-click the node to configure it with source set to \"Listen for broadcast messages\", and configure it to listen on all instances and devices with the topic that should match the same topic you configured in the Project Out node earlier to subscribe to your data that was sent before.",[427,1068,1069],{},[12,1070,1071,1073],{},[236,1072,1036],{}," The Project In node is used here to confirm successful transmission when using Project Out nodes. If you are using other output nodes such as MQTT Out, HTTP Request, or database nodes, replace the Project In node with the corresponding confirmation mechanism for your chosen protocol. For example, if your output node such as HTTP Request responds with a status code or success message, you can use that response directly for confirmation instead of the Project In node.",[285,1075,1076],{"start":62},[233,1077,406,1078,450,1080,1082,1083],{},[236,1079,449],{},[236,1081,1065],{}," node. Name it \"Prepare Record ID\" and configure the following rules:\n",[230,1084,1085,1097],{},[233,1086,1087,467,1089,471,1091,1093,1094,1096],{},[236,1088,466],{},[50,1090,470],{},[50,1092,474],{}," (JSONata expression: ",[50,1095,474],{},")",[233,1098,1099,467,1101,471,1104],{},[236,1100,480],{},[50,1102,1103],{},"msg.params.$record_id",[50,1105,856],{},[12,1107,1108,1112],{},[311,1109],{"alt":1110,"dataZoomable":48,"src":1111},"Change node preparing parameters for marking record as sent","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fset-params-step-5.png",[316,1113,1110],{},[285,1115,1116,1120],{"start":68},[233,1117,543,1118,425],{},[236,1119,424],{},[233,1121,788,1122,450,1124,1126,1127,1129],{},[236,1123,791],{},[236,1125,449],{}," node. Name it \"Mark as Sent\", then double-click it to configure. Select your database, set SQL Query mode to ",[236,1128,522],{},", and enter the following SQL:",[43,1131,1133],{"className":329,"code":1132,"language":331,"meta":48,"style":48},"   UPDATE data_buffer \n   SET sent = 1 \n   WHERE id = $record_id;\n",[50,1134,1135,1140,1145],{"__ignoreMap":48},[53,1136,1137],{"class":55,"line":56},[53,1138,1139],{},"   UPDATE data_buffer \n",[53,1141,1142],{"class":55,"line":62},[53,1143,1144],{},"   SET sent = 1 \n",[53,1146,1147],{"class":55,"line":68},[53,1148,1149],{},"   WHERE id = $record_id;\n",[285,1151,1152,1156],{"start":81},[233,1153,543,1154,425],{},[236,1155,424],{},[233,1157,509,1158,1160,1161,1129],{},[236,1159,791],{}," node onto the canvas and connect it to the previous SQLite node. Name it \"Delete Record\", then double-click it to configure. Select database, set SQL Query mode to ",[236,1162,522],{},[43,1164,1166],{"className":329,"code":1165,"language":331,"meta":48,"style":48},"   DELETE FROM data_buffer\n   WHERE id = $record_id\n   AND sent = 1;\n",[50,1167,1168,1173,1178],{"__ignoreMap":48},[53,1169,1170],{"class":55,"line":56},[53,1171,1172],{},"   DELETE FROM data_buffer\n",[53,1174,1175],{"class":55,"line":62},[53,1176,1177],{},"   WHERE id = $record_id\n",[53,1179,1180],{"class":55,"line":68},[53,1181,1182],{},"   AND sent = 1;\n",[285,1184,1185],{"start":93},[233,1186,543,1187,1189],{},[236,1188,424],{}," to save and deploy the flow.",[771,1191,742],{"id":1192},"handle-errors-and-disconnections",[285,1194,1195,1201,1207],{},[233,1196,406,1197,1200],{},[236,1198,1199],{},"Catch"," node onto the canvas. Configure it to catch errors from all nodes.",[233,1202,406,1203,450,1205,453],{},[236,1204,449],{},[236,1206,1199],{},[233,1208,1209,1210],{},"Name it \"Set Flow Error\" and configure it:",[230,1211,1212],{},[233,1213,1214,467,1216,471,1218,704],{},[236,1215,466],{},[50,1217,735],{},[50,1219,703],{},[12,1221,1222,1226],{},[311,1223],{"alt":1224,"dataZoomable":48,"src":1225},"Change node setting error flag when transmission fails","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fset-flow-error-flag.png",[316,1227,1224],{},[285,1229,1230,1234,1244,1249,1264,1270,1283],{"start":74},[233,1231,543,1232,425],{},[236,1233,424],{},[233,1235,406,1236,1239,1240,1243],{},[236,1237,1238],{},"Status"," node onto the canvas and configure it to monitor the ",[236,1241,1242],{},"Project"," node's status.",[233,1245,406,1246,1248],{},[236,1247,599],{}," node onto the canvas and connect it to the status node.",[233,1250,1251,1252,952,1255,1258,1259,956,1262,425],{},"Name it \"Check Disconnected\", set the Property to ",[50,1253,1254],{},"msg.status.text",[50,1256,1257],{},"=="," with value ",[50,1260,1261],{},"disconnected",[236,1263,424],{},[233,1265,406,1266,450,1268,453],{},[236,1267,449],{},[236,1269,599],{},[233,1271,1272,1273],{},"Name it \"Set Network Failure Flag\" and configure it:",[230,1274,1275],{},[233,1276,1277,467,1279,471,1281,704],{},[236,1278,466],{},[50,1280,669],{},[50,1282,617],{},[233,1284,543,1285,1287],{},[236,1286,424],{}," to save and deploy your flow.",[32,1289,1291],{"id":1290},"conclusion","Conclusion",[12,1293,1294],{},"You now have a working store-and-forward system that protects your data during network failures.",[12,1296,1297],{},"When the network is up, data flows through the buffer and transmits immediately. When the network goes down, data accumulates in SQLite. When connectivity returns, the buffered data forwards automatically while new data continues collecting. No data is lost, regardless of how long the outage lasts.",[12,1299,1300],{},"This pattern solves a common problem in industrial environments: maintaining complete time-series data when network infrastructure fails. Your production systems can now operate independently of network reliability.",[12,1302,1303],{},"The system you've built is production-ready as-is, but you can extend it based on your requirements, add monitoring for buffer capacity, implement data validation rules, or configure forwarding to multiple destinations. The core mechanism remains the same.",[12,1305,1306,1307,273],{},"If you want to get the flow template that you can use directly and modify according to your needs, check out our ",[269,1308,1310],{"href":1309},"\u002Fblueprints\u002Fgetting-started\u002Fstore-and-forward\u002F","latest blueprint",[12,1312,1313,1314,273],{},"Store-and-forward is just one part of a complete PLC integration. For the full picture, connecting Siemens, Allen-Bradley, Omron, and other PLCs to MQTT, cloud, and enterprise systems, see the ",[269,1315,1317],{"href":1316},"\u002Flanding\u002Fplc\u002F","FlowFuse PLC integration overview",[1319,1320,1321],"style",{},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":48,"searchDepth":74,"depth":74,"links":1323},[1324,1325,1340],{"id":34,"depth":62,"text":35},{"id":213,"depth":62,"text":214,"children":1326},[1327,1328,1329,1330,1331,1332,1335],{"id":224,"depth":68,"text":225},{"id":254,"depth":68,"text":255},{"id":276,"depth":68,"text":277},{"id":397,"depth":68,"text":398},{"id":556,"depth":68,"text":557},{"id":765,"depth":68,"text":766,"children":1333},[1334],{"id":773,"depth":74,"text":774},{"id":924,"depth":68,"text":925,"children":1336},[1337,1338,1339],{"id":931,"depth":74,"text":932},{"id":1057,"depth":74,"text":1058},{"id":1192,"depth":74,"text":742},{"id":1290,"depth":62,"text":1291},null,"2025-11-21","Learn how to implement store-and-forward buffering for data collection. This guide shows you how to build an edge system with FlowFuse that maintains complete data continuity during network outages, preventing production data loss and compliance gaps.","md","\u002Fblog\u002F2025\u002F11\u002Fimages\u002Fstore-and-forward.png","2026-06-17",{"keywords":1348,"excerpt":1349},"store-and-forward, edge computing, PLC data buffering, network resilience, industrial IoT, data continuity, FlowFuse, SQLite buffering, SCADA data collection, network outage recovery",{"type":9,"value":1350},[1351],[12,1352,14],{},"\u002Fblog\u002F2025\u002F11\u002Fstore-and-forward-edge-data-buffering",{"title":5,"description":1343},{"loc":1353},"blog\u002F2025\u002F11\u002Fstore-and-forward-edge-data-buffering","Keep collecting data when your network goes down",[1359,1360],"flowfuse","plc","Network outages leave PLCs running while their data has nowhere to go, creating gaps in production records, audit trails, and compliance documentation. Store-and-forward solves this by writing every data point to a local SQLite buffer first, then forwarding it when connectivity is available. This guide builds the pattern in FlowFuse and Node-RED across six steps, covering data collection, SQLite buffering, connectivity monitoring with a ping node, batched forwarding of unsent records, and error handling, so no data is lost regardless of how long the outage lasts.","022AlnkI-kPQmHojIy5bpdZz0nS3BYfvR_Fgs9ps8hs",{"id":1364,"extension":1365,"meta":1366,"sections":1367,"stem":1756,"__hash__":1757},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[1368,1419,1520,1582,1659,1738],{"id":1369,"title":1370,"features":1371},"ai-automation","AI & Automation",[1372,1382,1392,1402,1408,1414],{"id":1373,"title":1374,"description":1375,"docsLink":1376,"changelog":1377,"tiers":1381},"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",[1378],{"url":1379,"release":1380},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":77,"hub":77,"fleet":77},{"id":1383,"title":1384,"description":1385,"docsLink":1386,"changelog":1387,"subfeature":77,"showOnPricing":1390,"tiers":1391},"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",[1388],{"url":1389,"release":1380},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":77,"hub":77,"fleet":77},{"id":1393,"title":1394,"description":1395,"docsLink":1396,"changelog":1397,"subfeature":77,"showOnPricing":1390,"tiers":1401},"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",[1398],{"url":1399,"release":1400},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":77,"hub":77,"fleet":77},{"id":1403,"title":1404,"description":1405,"docsLink":1406,"subfeature":77,"beta":77,"showOnPricing":1390,"tiers":1407},"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":77,"hub":77,"fleet":77},{"id":1409,"title":1410,"description":1411,"docsLink":1412,"tiers":1413},"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":77,"hub":77,"fleet":77},{"id":1415,"title":1416,"description":1417,"tiers":1418},"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":77,"hub":77,"fleet":77},{"id":1420,"title":1421,"features":1422},"build","Build",[1423,1429,1435,1445,1451,1457,1461,1467,1473,1481,1487,1491,1495,1504,1512],{"id":1424,"title":1425,"description":1426,"docsLink":1427,"tiers":1428},"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":77,"hub":1390,"fleet":77},{"id":1430,"title":1431,"description":1432,"docsLink":1433,"tiers":1434},"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":77,"hub":77,"fleet":77},{"id":1436,"title":1437,"description":1438,"docsLink":1439,"changelog":1440,"tiers":1444},"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",[1441],{"url":1442,"release":1443},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":77,"hub":77,"fleet":77},{"id":1446,"title":1447,"description":1448,"docsLink":1449,"tiers":1450},"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":77,"hub":77,"fleet":77},{"id":1452,"title":1453,"description":1454,"docsLink":1455,"showOnPricing":1390,"tiers":1456},"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":77,"hub":77,"fleet":77},{"id":1458,"title":1459,"showOnPricing":1390,"tiers":1460},"static-assets","Static Assets",{"edge":77,"hub":77,"fleet":77},{"id":1462,"title":1463,"description":1464,"docsLink":1465,"tiers":1466},"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":77,"hub":77,"fleet":77},{"id":1468,"title":1469,"description":1470,"docsLink":1471,"tiers":1472},"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":77,"hub":77,"fleet":77},{"id":1474,"title":1475,"description":1476,"changelog":1477,"subfeature":77,"showOnPricing":1390,"tiers":1480},"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.",[1478],{"url":1479,"release":1443},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1482,"title":1483,"description":1484,"docsLink":1485,"tiers":1486},"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":77,"hub":77,"fleet":77},{"id":1488,"title":1489,"subfeature":77,"showOnPricing":1390,"tiers":1490},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":77,"hub":1390,"fleet":77},{"id":1492,"title":1493,"subfeature":77,"showOnPricing":1390,"tiers":1494},"blueprints-it-apps","Blueprints - IT APPS",{"edge":1390,"hub":77,"fleet":1390},{"id":1496,"title":1497,"description":1498,"changelog":1499,"showOnPricing":1390,"tiers":1503},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[1500],{"url":1501,"release":1502},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":77,"hub":77,"fleet":77},{"id":1505,"title":1506,"description":1507,"changelog":1508,"showOnPricing":1390,"tiers":1511},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[1509],{"url":1510,"release":1400},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1513,"title":1514,"description":1515,"changelog":1516,"showOnPricing":1390,"tiers":1519},"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.",[1517],{"url":1518,"release":1502},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1521,"title":1522,"features":1523},"deploy","Deploy",[1524,1530,1539,1545,1551,1557,1563,1569,1574],{"id":1525,"title":1526,"description":1527,"docsLink":1528,"tiers":1529},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":77,"hub":77,"fleet":77},{"id":1531,"title":1532,"description":1533,"docsLink":1534,"changelog":1535,"tiers":1538},"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",[1536],{"url":1537,"release":1380},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":77,"hub":1390,"fleet":77},{"id":1540,"title":1541,"description":1542,"docsLink":1543,"tiers":1544},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":1390,"hub":77,"fleet":1390},{"id":1546,"title":1547,"description":1548,"docsLink":1549,"tiers":1550},"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":77,"hub":1390,"fleet":77},{"id":1552,"title":1553,"description":1554,"docsLink":1555,"showOnPricing":1390,"tiers":1556},"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":77,"hub":77,"fleet":77},{"id":1558,"title":1559,"description":1560,"docsLink":1561,"tiers":1562},"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":77,"hub":77,"fleet":77},{"id":1564,"title":1565,"description":1566,"docsLink":1567,"tiers":1568},"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":1390,"hub":77,"fleet":1390},{"id":1570,"title":1571,"description":1572,"docsLink":1567,"subfeature":77,"showOnPricing":1390,"tiers":1573},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":1390,"hub":77,"fleet":1390},{"id":1575,"title":1576,"description":1577,"docsLink":1567,"changelog":1578,"subfeature":77,"showOnPricing":1390,"tiers":1581},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[1579],{"url":1580,"release":1502},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":1390,"hub":77,"fleet":1390},{"id":1583,"title":1584,"features":1585},"operate-maintain","Operate & Maintain",[1586,1592,1598,1603,1611,1615,1619,1624,1630,1636,1641,1647,1651,1655],{"id":1587,"title":1588,"description":1589,"docsLink":1590,"tiers":1591},"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":77,"hub":77,"fleet":77},{"id":1593,"title":1594,"description":1595,"docsLink":1596,"subfeature":77,"showOnPricing":1390,"tiers":1597},"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":77,"hub":77,"fleet":77},{"id":1599,"title":1600,"description":1601,"docsLink":1596,"subfeature":77,"showOnPricing":1390,"tiers":1602},"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":77,"hub":77,"fleet":77},{"id":1604,"title":1605,"description":1606,"changelog":1607,"subfeature":77,"showOnPricing":1390,"tiers":1610},"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.",[1608],{"url":1609,"release":1502},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1612,"title":1613,"subfeature":77,"showOnPricing":1390,"tiers":1614},"version-history-timeline","Version History Timeline",{"edge":77,"hub":77,"fleet":77},{"id":1616,"title":1617,"tiers":1618},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":77,"hub":77,"fleet":77},{"id":1620,"title":1621,"description":1622,"tiers":1623},"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":77,"hub":1390,"fleet":77},{"id":1625,"title":1626,"description":1627,"docsLink":1628,"tiers":1629},"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":77,"hub":1390,"fleet":77},{"id":1631,"title":1632,"description":1633,"docsLink":1634,"tiers":1635},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":1390,"hub":77,"fleet":1390},{"id":1637,"title":1638,"description":1639,"tiers":1640},"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":77,"hub":77,"fleet":77},{"id":1642,"title":1643,"description":1644,"docsLink":1645,"subfeature":77,"showOnPricing":1390,"tiers":1646},"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":77,"hub":77,"fleet":77},{"id":1648,"title":1649,"subfeature":77,"showOnPricing":1390,"tiers":1650},"email-alerts","Email Alerts",{"edge":77,"hub":77,"fleet":77},{"id":1652,"title":1653,"showOnPricing":1390,"tiers":1654},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":77,"hub":77,"fleet":77},{"id":1656,"title":1657,"tiers":1658},"protected-instances","Protected Instances",{"edge":1390,"hub":77,"fleet":1390},{"id":1660,"title":1661,"features":1662},"govern-secure","Govern and Secure",[1663,1672,1678,1684,1689,1695,1701,1707,1715,1721,1727,1733],{"id":1664,"title":1665,"description":1666,"docsLink":1667,"changelog":1668,"tiers":1671},"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",[1669],{"url":1670,"release":1443},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1673,"title":1674,"description":1675,"docsLink":1676,"tiers":1677},"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":77,"hub":77,"fleet":77},{"id":1679,"title":1680,"description":1681,"docsLink":1682,"tiers":1683},"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":1390,"hub":77,"fleet":77},{"id":1685,"title":1686,"description":1687,"tiers":1688},"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":77,"hub":1390,"fleet":1390},{"id":1690,"title":1691,"description":1692,"docsLink":1693,"tiers":1694},"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":77,"hub":77,"fleet":77},{"id":1696,"title":1697,"description":1698,"docsLink":1699,"tiers":1700},"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":77,"hub":77,"fleet":77},{"id":1702,"title":1703,"description":1704,"docsLink":1705,"subfeature":77,"showOnPricing":1390,"tiers":1706},"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":77,"hub":77,"fleet":77},{"id":1708,"title":1709,"description":1710,"changelog":1711,"subfeature":77,"showOnPricing":1390,"tiers":1714},"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.",[1712],{"url":1713,"release":1443},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":77,"hub":77,"fleet":77},{"id":1716,"title":1717,"description":1718,"docsLink":1719,"showOnPricing":1390,"tiers":1720},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":77,"hub":77,"fleet":77},{"id":1722,"title":1723,"description":1724,"docsLink":1725,"showOnPricing":1390,"tiers":1726},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":77,"hub":77,"fleet":77},{"id":1728,"title":1729,"description":1730,"docsLink":1731,"tiers":1732},"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":1390,"hub":77,"fleet":1390},{"id":1734,"title":1735,"description":1736,"tiers":1737},"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":1390,"hub":77,"fleet":1390},{"id":1739,"title":1740,"features":1741},"support","Support",[1742,1747,1751],{"id":1743,"title":1744,"docsLink":1745,"tiers":1746},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":77,"hub":77,"fleet":77},{"id":1748,"title":1749,"showOnPricing":1390,"tiers":1750},"live-chat-support","Live Chat Support",{"edge":77,"hub":77,"fleet":77},{"id":1752,"title":1753,"docsLink":1754,"tiers":1755},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":77,"hub":77,"fleet":77},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[1759,1762,1765,1768,1771,1774,1776,1779,1782,1785,1788,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1903,1906,1909,1912,1915,1918,1921,1924,1926,1929,1932,1935,1938,1941,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2019,2022,2025,2028,2031,2034,2037,2040,2043,2046,2049,2052,2055,2058,2061,2064,2067,2070,2073,2075,2078,2081,2084,2087,2090,2093,2096,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2250,2253,2256,2259,2262,2265,2268,2271,2274,2277,2280,2283,2286,2289],{"path":1760,"title":1761},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":1763,"title":1764},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":1766,"title":1767},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":1769,"title":1770},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":1772,"title":1773},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":1775,"title":1483},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":1777,"title":1778},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":1780,"title":1781},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":1783,"title":1784},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":1786,"title":1787},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":1789,"title":1674},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":1791,"title":1792},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":1794,"title":1795},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":1797,"title":1798},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":1800,"title":1801},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":1803,"title":1804},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":1806,"title":1807},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":1809,"title":1810},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":1812,"title":1813},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":1815,"title":1816},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":1818,"title":1819},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":1821,"title":1822},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":1824,"title":1825},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":1827,"title":1828},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":1830,"title":1831},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":1833,"title":1834},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":1836,"title":1837},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":1839,"title":1840},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":1842,"title":1843},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":1845,"title":1846},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":1848,"title":1849},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":1851,"title":1852},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":1854,"title":1855},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":1857,"title":1858},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":1860,"title":1861},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":1863,"title":1864},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":1866,"title":1867},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":1869,"title":1870},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":1872,"title":1873},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":1875,"title":1876},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":1878,"title":1879},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":1881,"title":1882},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":1884,"title":1885},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1887,"title":1888},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1890,"title":1891},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1893,"title":1894},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1896,"title":1897},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1899,"title":1900},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1902,"title":1900},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1904,"title":1905},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1907,"title":1908},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1910,"title":1911},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1913,"title":1914},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1916,"title":1917},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1919,"title":1920},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1922,"title":1923},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1925,"title":1923},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1927,"title":1928},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1930,"title":1931},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1933,"title":1934},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1936,"title":1937},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1939,"title":1940},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1942,"title":1940},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1944,"title":1945},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1947,"title":1948},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1950,"title":1951},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1953,"title":1954},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1956,"title":1957},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1959,"title":1960},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1962,"title":1963},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1965,"title":1966},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1968,"title":1969},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1971,"title":1972},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1974,"title":1613},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1976,"title":1977},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1979,"title":1980},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1982,"title":1983},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1985,"title":1986},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1988,"title":1989},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1991,"title":1992},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1994,"title":1995},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1997,"title":1998},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":2000,"title":2001},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":2003,"title":2004},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":2006,"title":2007},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":2009,"title":2010},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":2012,"title":2013},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":2015,"title":2016},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":2018,"title":1613},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":2020,"title":2021},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":2023,"title":2024},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":2026,"title":2027},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":2029,"title":2030},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":2032,"title":2033},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":2035,"title":2036},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":2038,"title":2039},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":2041,"title":2042},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":2044,"title":2045},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":2047,"title":2048},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":2050,"title":2051},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":2053,"title":2054},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":2056,"title":2057},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":2059,"title":2060},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":2062,"title":2063},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":2065,"title":2066},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":2068,"title":2069},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":2071,"title":2072},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":2074,"title":2072},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":2076,"title":2077},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":2079,"title":2080},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":2082,"title":2083},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":2085,"title":2086},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":2088,"title":2089},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":2091,"title":2092},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":2094,"title":2095},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":2097,"title":1437},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":2099,"title":2100},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":2102,"title":2103},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":2105,"title":2106},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":2108,"title":2109},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":2111,"title":2112},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":2114,"title":2115},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":2117,"title":2118},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":2120,"title":2121},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":2123,"title":2124},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":2126,"title":2127},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":2129,"title":2130},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":2132,"title":2133},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":2135,"title":2136},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":2138,"title":2139},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":2141,"title":2142},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":2144,"title":2145},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":2147,"title":2148},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":2150,"title":2151},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":2153,"title":2154},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":2156,"title":2157},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":2159,"title":2160},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":2162,"title":2163},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":2165,"title":2166},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":2168,"title":2169},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":2171,"title":2172},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":2174,"title":2175},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":2177,"title":2178},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":2180,"title":2181},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":2183,"title":2184},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":2186,"title":2187},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":2189,"title":2190},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":2192,"title":2193},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":2195,"title":2196},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":2198,"title":2199},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":2201,"title":2202},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":2204,"title":2205},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":2207,"title":2208},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":2210,"title":2211},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":2213,"title":2214},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":2216,"title":2217},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":2219,"title":2220},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":2222,"title":2223},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":2225,"title":2226},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":2228,"title":2229},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":2231,"title":2232},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":2234,"title":2235},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":2237,"title":2238},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":2240,"title":2241},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":2243,"title":2244},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":2246,"title":2247},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":2249,"title":1506},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":2251,"title":2252},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":2254,"title":2255},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":2257,"title":2258},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":2260,"title":2261},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":2263,"title":2264},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":2266,"title":2267},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":2269,"title":2270},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":2272,"title":2273},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":2275,"title":2276},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":2278,"title":2279},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":2281,"title":2282},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":2284,"title":2285},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":2287,"title":2288},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":2290,"title":2291},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105897338]