I have a scheduler handling periodic task. This task is using data constant as a part of filter used for loading data. If the constant value is changed via UI, the scheduler doesn’t reflect it. It needs to be restarted to work with the new value.
I’d expect Scheduler to start working with new value without need to restart it.
There is similar issue when running multiple instances of Origam in IIS. When data constant is changed in one instance, the new value is not reflected in other instances until instance recycle. The workaround for this behavior is to lookup the constant value by its Id.
Yes, this is a duplicate of Constant caching between instances issue
Also I auggest to solve it together with SqlAdapterCache Replacement Policy by introducing cache timers for user caches. And make the timers configurable for each cache type so when it times out it would reload on first use.
It’s not a bug as it was never intended to be working.