Process flow runs cached version of data mapper

Situation:

I've made a number of changes to a data mapper. At some point yesterday, Adeptia stopped using any changes I attempt to add. When I pull up the data mapper and run it, the results are different from when I call the process flow externally. The Data Mapper version contains expected results.

It is as though it has cached an earlier version of the mapper and uses it instead of the current.

I've cleared my Java cache and rebooted my machine. Could this be caching at the server level?

 

Suggestion:

Verify the mapping used in the process flow is still the mapping you are editing. You can confirm this by comparing the "Entity Id" of the mapping activity with the ID value of the activity when selecting it in the process flow (properties panel).

 

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.