Cancelling idxactivate leaves the index in partially active state and does not prevent using the index in ABL
If an idxactivate operation is cancelled, either by the user or it is unexpectedly ended by some other event (db crash, etc) the _index._active flag remains TRUE and the client doesn't ignore the index when compiling.