webMethods

 View Only

 Getting error while Exporting/Cloning services from webMethods.IO Integration

Atul Jha's profile image
Atul Jha posted Fri July 18, 2025 05:36 AM

Hi All,

I am getting a weird error whenever I try to export or clone services from wM.IO Integration. 

Clone failed: The asset xyz cannot be copied as it is not consistent.
This operation can not be performed as Integration[s] abc are in inconsistent state.
Now, why it is occurring and what resolution steps are there, please advise.
To add - If I try to copy the steps in another project's service, it is also not allowing.
Giving the below error - 
Error Services not valid: Avoid copying and pasting invalid services
Thanks in advance!
Bastiaan Rodenburg's profile image
Bastiaan Rodenburg

Often this is caused by refrencing another flow service that is not part of this project. This is not alowed in wM.IO but sometimes one can manage to do this anyway. For example by copy/paste are import/export services that are referencing each other. Design time everything will be working correct but exporting or publishing is not possible anymore. Likely you are using a flow service that exists in another project as well. Focus on that situations and manualy redo that part! Can also be the case with using document types that exists in other projects. I don't have found a proper solution for this yet except redoing a lot of your stuff.

Atul Jha's profile image
Atul Jha

@Bastiaan Rodenburg,
Thank you for your response. The thing is - Yes. There is a reference to a generic error handling service (from another project), which I am calling via HTTP. But that doesn't seem to be the issue (at least not so far). So, what I did was - I manually created the service in another environment. But the issue still persisted. Upon several trial and errors, it was found that there was a DISABLED sequence (which I was using for debugging purpose) which might have been causing the issue. Now, I am not too sure about that. But when I deleted that step and then tried exporting, it worked.

Imagine things working well in lower environment. And when you go for the go-live, you have to manually redo the code in prod itself just because the project's state is inconsistent. Not a good thing, in my view.

To be honest, it is very difficult to get the root cause of issues like these. Feels like as a developer, I do not have much control of the things. I feel On-prem designer is great in this regard.

Anyway, would have been great, if there could be a detailed analysis on such issues. :) 

Thanks,

Atul Kumar Jha