Skip to main content

Delete Task

Deletes a completed or pending ABBYY Cloud processing task.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.

Inputs​

  • Task ID - ID of the ABBYY task to delete.

Options​

This node has no configurable options.

Outputs​

  • Task Status - Status of the deleted task confirming deletion.

How It Works​

The Delete Task node removes a task from ABBYY Cloud. When executed, the node:

  1. Validates the task ID is not empty
  2. Sends a delete request to ABBYY Cloud API
  3. Removes the task and its associated data
  4. Returns confirmation of deletion

Requirements​

  • Valid ABBYY Cloud credentials
  • Valid task ID from a previously created task

Error Handling​

The node will return specific errors in the following cases:

  • Robomotion.ABBYYCloud.ErrTaskID - Task ID is invalid or empty

Usage Example​

Scenario: Complete workflow with cleanup

1. Process Image node:
   - Image Path: "C:/images/document.jpg"
   - Output: {{ $.task }}

2. Wait Task node:
   - Task: {{ $.task }}
   - Timeout: 60

3. Download or process results from {{ $.status }}

4. Delete Task node:
   - Task ID: {{ $.task.id }}

Scenario: Cleanup after batch processing

1. Loop through documents:
   a. Process Image
   b. Wait Task
   c. Extract results
   d. Delete Task (cleanup)

2. All tasks are cleaned up automatically

Common Use Cases​

  • Resource Cleanup - Free up cloud storage and task quota
  • Privacy Compliance - Remove sensitive data after processing
  • Quota Management - Manage concurrent task limits
  • Workflow Completion - Clean up after successful processing
  • Error Recovery - Delete failed tasks before retry
  • Batch Processing - Clean up tasks after each iteration

Task Deletion Behavior​

  • Completed Tasks: Can be deleted immediately after retrieving results
  • Processing Tasks: Can be deleted to cancel processing
  • Failed Tasks: Should be deleted to free resources
  • Queued Tasks: Deletion cancels queued processing

Tips and Best Practices​

  • When to Delete:
    • After downloading all results
    • After extracting needed data
    • When task is no longer needed
    • To free up quota for new tasks
    • After processing failures
  • When NOT to Delete:
    • Before retrieving results
    • If results might be needed later
    • During active processing (unless canceling)
    • If task ID needs to be referenced
  • Best Practices:
    • Always delete tasks after completion
    • Delete in error handlers for failed tasks
    • Use Continue On Error for robust cleanup
    • Track deleted task IDs if needed
    • Delete oldest tasks first if quota is limited
  • Quota Management:
    • Check your ABBYY Cloud task quota limits
    • Delete completed tasks to free quota
    • Monitor active task count
    • Implement cleanup in all workflows
    • Set up periodic cleanup for orphaned tasks
  • Data Privacy:
    • Delete tasks containing sensitive data
    • Implement retention policies
    • Delete tasks on workflow failure
    • Consider immediate deletion for PII
    • Document deletion in audit logs
  • Error Handling:
    • Enable Continue On Error for cleanup steps
    • Don't fail workflow on cleanup errors
    • Log deletion failures for monitoring
    • Retry deletion if initially fails
    • Handle already-deleted tasks gracefully
  • Workflow Patterns:
    • Simple: Process → Wait → Use Results → Delete
    • Error Handler: Try processing → Catch error → Delete task
    • Batch: Loop with delete at end of each iteration
    • Conditional: Delete only if processing succeeds
  • Performance:
    • Deletion is a fast operation
    • No credit consumption for deletion
    • Can delete multiple tasks in parallel
    • Batch deletions for efficiency
  • Resource Management:
    • Downloaded results persist after deletion
    • Task data is permanently removed
    • Cannot retrieve task status after deletion
    • Plan result extraction before deletion
  • Production Considerations:
    • Implement automatic cleanup
    • Monitor task accumulation
    • Set up alerts for quota limits
    • Regular cleanup jobs for orphaned tasks
    • Test cleanup in error scenarios
  • Common Mistakes:
    • Deleting before downloading results
    • Not deleting on error paths
    • Ignoring deletion failures
    • Not handling quota limits
    • Leaving orphaned tasks