Simply, how do we ensure that the values of a custom field are current when running on a job thread via the CustomFieldManager
?
Less simply, we are running a job in another thread to disconnect processing from the EventListener thread. We notice that the value of a custom field differs when accessed from inside the EventListener execution thread (value is current and correct) versus a separate thread (value is old and incorrect). Attempts to use the same CustomFieldManager
in both places still results in different values. This seems to indicate a thread-local cache, but we see no way to clear the cache or force an update of the cached value (have tried refresh()
and clear()
in CustomFieldManager
).