Without knowing how the FTP directory is populated, you might have an issue with the ListFTP state and might consider changing its its Listing Strategy, However assuming that is no issue and you want to only perform an action based on any file with a naming structure like this: xxxx-xxxx-xxxx-xxxx-20220121110000-xxxx-xxxx.csv and only if it is older than two hours from "now" I would run the output of your ListFTP to an UpdateAttribute and add these 2 properties:   property name        fileTime          value ${filename:getDelimitedField(5,'-'):trim():toDate('yyyyMMddHHmmss'):toNumber()} property name timeNow                      value ${now():toNumber():minus(7200000)}   Then route that to a RouteOnAttribute and add a new property:   property name              value 2 hours old                ${fileTime:le(${timeNow})}   Then you can drag that connection to follow on processing and the unmatched connection to other processing or terminate it.   Explanation: filelName ${filename:getDelimitedField(5,'-'):trim():toDate('yyyyMMddHHmmss'):toNumber()} This grabs the time out of your filename and converts it to a Date object so it can be converted to its epoch representation   timeNow ${now():toNumber():minus(7200000)} Sets a value 2 hours ago from current time     ${fileTime:le(${timeNow})} If attribute fileName is less than or equal to timeNow it means that it is 2 hours old.       ... View more

Reading your sample log messages closer I can see that the coordinator received a heartbeat from node 3   "2022-01-19 16:04:52,573 INFO [Process Cluster Protocol Request-30] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 35f2ed1a-ca6f-4cc6-ab4a-6c0774fc9c6d (type=HEARTBEAT, length=2837 bytes) from nifi-hatest-03:9091 in 19 millis"   So I also wonder if we have a caching rendering issue, can you see what the UI shows using incognito mode? And finally if this is a DEV environment you can also try and delete your local state directory, that value is set in file "state-management.xml"   Deleting state will clear out any local state your processors might depend on if configured as such, so remove with caution. It will also clear out cluster node ID's it local knows of. ... View more