Error OK when publishing / activating Flow and SubflowDescription"Error OK" Error message is seen when publishing / activating Flow and SubflowRelease or EnvironmentAll VersionsCauseIt is expected behavior for the flow not to publish when it has a recursive call to itself as documented here:https://docs.servicenow.com/csh?topicname=flow-designer-arch-overview.html&version=latest#d1008146e790The transaction is being timed out and hence we get the error message as "Error OK"Stack Trace: Transaction cancelled: maximum execution time exceeded: com.glide.rest.util.RESTRuntimeException: Transaction cancelled: maximum execution time exceeded: com.glide.rest.serializer.impl.JSONSerializer.handleSerializeException(JSONSerializer.java:166)com.glide.rest.serializer.impl.JSONSerializer.serializeServiceResult(JSONSerializer.java:60)com.glide.rest.handler.impl.ServiceResultHandlerImpl.serialize(ServiceResultHandlerImpl.java:130)com.glide.rest.handler.impl.ServiceResultHandlerImpl.processServiceResultBody(ServiceResultHandlerImpl.java:96)com.glide.rest.handler.impl.ServiceResultHandlerImpl.processServiceResult(ServiceResultHandlerImpl.java:40)com.glide.rest.processors.RESTAPIProcessor.process(RESTAPIProcessor.java:290)com.glide.processors.AProcessor.runProcessor(AProcessor.java:553)com.glide.processors.AProcessor.processTransaction(AProcessor.java:241)com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:177)com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:166)com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:31)com.glide.sys.Transaction.run(Transaction.java:2218)java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)java.lang.Thread.run(Thread.java:748)ResolutionThe reason we DON'T allow recursive calls is to prevent instance outages and consumption of system resources. Consider re-designing the flow.