We had the case that the ACK of an operation always changed in case of an error and the following messages always threw an error although everything was ok. A restart has then always helped until the next error.
Solution was to catch the ACK in the router and check it. If the error was found a TRACE was executed in which ##class(Ens.Director).EnableConfigItem() was called.
Return Value is the status ;)
- Log in to post comments