Update an intent either with batch or single operation loses the end of conversation flag

[asavvop]

Hi guys,

It seems that after using either the BatchUpdateIntentsAsync or UpdateIntentAsync calls from the client api results in the intent losing the state of whether this intent is the end of the conversation.
Note: The used intent name has not been changed at all.

Is there anyway to read the state of this flag or force an update of this flag?

Thanks

[markusrt]

@asavvop We had a similar issue in our project. Maybe you did had a consistent model zip in your restore. This is crucial as end intends are referenced via their id in agent.json