I recently noticed this on NiFi startup of a standalone instance even though I hadn't changed the flow in the meantime:
2024-07-23 14:54:29,559 INFO [main] o.a.n.c.s.StandardProcessScheduler Enabling StandardControllerServiceNode[service=JsonRecordSetWriter[id=e09a1886-0190-1000-cf4b-219dcc5cd740], name=ControllerJsonRecordSetWriter, active=false] 2024-07-23 14:54:59,566 INFO [main] o.a.n.c.s.StandardProcessScheduler Enabling StandardControllerServiceNode[service=LoggingRecordSink[id=e099d0c8-0190-1000-6c6e-3ced65b37c79], name=LoggingRecordSink, active=false] 2024-07-23 14:54:59,610 INFO [main] o.a.n.f.s.StandardVersionedComponentSynchronizer Updating StandardProcessGroup[identifier=e093123a-0190-1000-99e5-7d0a58c73b11,name=NiFi Flow] to org.apache.nifi.flow.VersionedExternalFlow@2db2b708; there are 11 differences to take into account: Processor with ID e09541c5-0190-1000-e56c-055331154880 exists in Proposed Flow but not in Currently Loaded Flow Connection with ID e0949308-0190-1000-6687-2d75cb063321 exists in Proposed Flow but not in Currently Loaded Flow Controller Service with ID e0964148-0190-1000-7bd7-dafc1e1e9366 exists in Proposed Flow but not in Currently Loaded Flow Processor with ID e094680b-0190-1000-2126-47be3080ac93 exists in Proposed Flow but not in Currently Loaded Flow Connection with ID e093d3cc-0190-1000-37ac-6dcdae031f1a exists in Proposed Flow but not in Currently Loaded Flow Connection with ID e094778f-0190-1000-7719-38608aba3d77 exists in Proposed Flow but not in Currently Loaded Flow Processor with ID e093a7c2-0190-1000-25a4-da6588eda8dc exists in Proposed Flow but not in Currently Loaded Flow Connection with ID e0957da4-0190-1000-43d4-31cd10da78f4 exists in Proposed Flow but not in Currently Loaded Flow Funnel with ID e09483f6-0190-1000-2ee8-887387914ec3 exists in Proposed Flow but not in Currently Loaded Flow Processor with ID e093e767-0190-1000-d8f3-2e1aefe682bb exists in Proposed Flow but not in Currently Loaded Flow Controller Service with ID e0965f87-0190-1000-af75-55f211b2b672 exists in Proposed Flow but not in Currently Loaded Flow Looks like it took 30 seconds to do the comparison and found differences in the proposed vs current flow. Is this expected? Thanks, Matt
