[CHORE] why UpdateRouteTable add UnchangedTriggers

[bxjg1987]

UpdateRouteTable.HandleAsync(WorkflowTriggersIndexed notification, CancellationToken cancellationToken)
await routeTableUpdater.AddRoutesAsync(notification.IndexedWorkflowTriggers.UnchangedTriggers, cancellationToken);

but why add UnchangedTriggers?

[sfmskywalker]

Good question. When the application starts, it needs to populate the RouteTable with existing triggers. Otherwise, the route table would remain empty until the user publishes HTTP workflows. Leep in mind that the RoutTable is an in-memory lookup and does not have its own persistence,

[sfmskywalker]

Closing as resolved: the explanation above covers why unchanged triggers populate the in-memory route table at startup, and the corresponding issue #6286 was closed. If you observe different behavior in a current release, please open a new issue with the Elsa version and a minimal reproduction.