The Stop Vision Process action is used to stop a Vision (image processing/object recognition/camera stream) process initiated on the Kuika platform. It is preferred in scenarios where real-time Vision Flows need to be terminated in a controlled manner.

This action safely terminates an active Vision process, freeing up system resources.

This action is supported in both web and mobile applications.

Technical Features

• Vision Flow Termination: Stops an active Vision process.
• Real-Time Stream Control: Controlled termination of camera or video-based workflows.
• Resource Management: Optimizes system resources by terminating GPU/CPU usage.
• Audit Log Support: When Enable Audit Logs is activated, the process can be logged.
• Validation Control: If desired, the process can be stopped without triggering validation.

Stop Vision Process Action Application Steps

Adding the Stop Vision Process Action

1. Log in to the Kuika platform.
2. Open the project you will be working on from the Apps screen.
3. Go to the UI Design module.

4. Select the button you want to stop the Vision process (for example, “Stop Detection”).
5. From the Properties panel on the right: ADD ACTION → OnClick (or relevant trigger) → Vision → Select the Stop Vision Process action.

Configuring Stop Vision Process Parameters

• visionFlow (Required): Specifies the reference of the Vision Flow to be stopped. Usually, the Vision Flow object obtained as a result of the Start Vision Process action is linked. Via the Symbol Picker: Action Results → Start Vision Process → visionFlow is selected to establish the link.
• Don't Trigger Validations (Optional): When enabled, validation rules on the page are not triggered during the stop process.
• Enable Audit Logs (Optional): The process is logged. Recommended for corporate use and traceability.

Usage Scenario: Stopping Real-Time Object Tracking

In a warehouse application, pallet tracking is performed via camera. When the user wants to manually terminate the process:

1. They press the “Stop Tracking” button.
2. The Stop Vision Process action is triggered.
3. The active Vision Flow is stopped.
4. The camera stream and analysis process end.

This eliminates unnecessary processing load.

Start–Stop Flow Logic

Stop Vision Process is typically used with the following flow:

1. Start Vision Process → Vision Flow is initiated,
2. Vision performs analysis,
3. User interaction or condition occurs,
4. Stop Vision Process → Process is terminated.

Calling Stop without first starting is not recommended; an active visionFlow reference must exist.

Advanced Customizations

• Conditional Stop: Stop Vision Process can be automatically executed when a specific threshold value is met.
• Use with State Control: The Stop action can be triggered based on the process state (e.g., stop if isProcessing = true).

Technical Risks

• Empty visionFlow Reference: The action does not work if the visionFlow parameter is empty.
• Already Stopped Process: An error may occur when attempting to stop the same flow again.
• Concurrently Running Flows: If the wrong reference is selected, a different vision process may be terminated.

The Stop Vision Process action ensures that Vision-based real-time processes are terminated in a safe and controlled manner.