Skip to main content
Question

Language cache refresh

  • Nov 4, 2026 9:29 AM UTC
  • 1 reply
  • 6 views

Forum|alt.badge.img+8

Dear Community, 

 

I would like to share with you a very strange behavior, you maybe have seen this before and have some idea. 

We are on IFS Apps10 UPD27, using IEE

We have 3 DBs: TEST, UAT and PROD

TEST and UAT sitting in the same DB server. PROD is in a separate one. 

When we are using TEST or UAT environments sometimes - looks completely randomly - we are starting to get strange error messages. 

Eg.: 

 

or in a different window:
 

 

or even more weird: in a completely standard window we are getting an error which says a boolean must have a value. But that field is not on the screen. When we are investigating we realized in the view behind the window contains a boolean value which has no value becuase the decode function can’t pull the TRUE/FALSE form the _db field. 

But after a language cache refresh the issue is solved. 

Do you have any idea why this is happening, how is possible to resolve and why this is only happening in our TEST and UAT - which are copies from PROD - but not in PROD environment? 

Have you ever seen this behavior previously?

 

Thank you very much in advance for all ideas! 

Kr, 

Balazs

1 reply

Sajid Ahmed
Do Gooder (Employee)
Forum|alt.badge.img+4
  • Do Gooder (Employee)
  • Nov 5, 2026 1:17 AM UTC

Hi ​@bapehu,

 

We’ve seen the same pattern: garbled messages and boolean/decode errors in views when language dictionary / domain PROG–DB lists are out of sync—often on non-prod clones with extra deployments and incomplete cache refresh. Refresh Language Cache fixes symptoms because it rebuilds those lists.

Fix: After each PROD clone and after each deploy to TEST/UAT, run Refresh Language Cache (all used languages), then Refresh Server Cache (Dictionary, then Reference), restart the app server, and have users start new sessions. Schedule periodic language refresh on TEST/UAT and check batch logs for failed/partial language refresh (custom LUs can break component refresh).

PROD usually stays clean because code and caches stay aligned; TEST/UAT don’t unless you automate that post-clone/post-deploy sequence.

 

Kind Regards,

Sajid Ahmed