Skip to main content
Question

Error executing Workflow "MetaDataModifiedException"

  • February 24, 2026
  • 2 replies
  • 14 views

REOGIRARD
Sidekick (Customer)
Forum|alt.badge.img+9

Hello,

I’m working on an automatization for unballasting parts multisite.
This is the second time QA is getting a metadata error executing the workflow.
We are using IFS Cloud 24r1, because we are under migration from IFS V8.

They are getting the following error when I inspect the HTTP call returning the error :

type: "MetaDataModifiedException"
message: "Error occurred due to metadata version miss match"

What does it mean ?
I have one deployed version only.
The workflow is triggered by a commandgroup (button) on shop order page.
Do I need to restart the middle-tiers, a specific pod when I am working on the workflow to make it work for users during tests ?

2 replies

Forum|alt.badge.img+9
  • Hero (Employee)
  • February 24, 2026

hi ​@REOGIRARD ,

one reason for such a thing to happen is if an API used inside the workflow got updated (metadata changed) and the projection cache is not yet refreshed. 

ref:Considerations Before Designing a Workflow - Technical Documentation For IFS Cloud

If this is the case there is an improvement done on this area that should mitigate this error and its available from 24R2 SU11, 25R1 SU5, 25R2 +

 


REOGIRARD
Sidekick (Customer)
Forum|alt.badge.img+9
  • Author
  • Sidekick (Customer)
  • February 25, 2026

Hi @kamn

Thank you for you answer.
That’s what I was thinking, but we did not updated APIs as it’s IFS standard even if we are on premise hosting.
It might be related to our customs but I don’t remember I made an update, and customs involved in the workflow are mine, for this specific case.
Is the projection cache related to dictionary cache ? From IFS aurena, there is no projection cache refresh option.
We gonna upgrade IFS to next SU then releases once the go-live happens for sure, hope this will help in future.

Thank you, have a nice day.

Guillaume