│ Grooper Help - Version 25.0
25.0.0017 2,127
  • Overview
  • Help Status

Activity Processing

Service Instance Grooper.Services

Executes unattended Code Activities as part of a Batch Process, providing scalable, parallel task processing for Grooper repositories.

Remarks

Overview

The Activity Processing service is Grooper's primary engine for automated, unattended work. It executes Code Activities—such as Image Processing, Recognize, Classify, and Extract—that perform the core steps of a Batch Process. All activities except for Review (which requires human intervention) are handled by this service.

At least one Activity Processing instance is required for every functional Grooper repository. You can scale processing by installing multiple service instances across different servers, and/or by increasing the thread count for each instance. Each thread operates independently, allowing for high-throughput, parallel task execution.

How It Works

  • The service hosts one or more Task Processor threads, each responsible for retrieving and executing Processing Tasks from a specified Processing Queue.
  • Each thread runs in the background, polling for new tasks, executing the associated Code Activity, and updating task and batch status as work is completed.
  • The service supports robust error handling, critical stop events, and detailed statistics tracking for all processing activity.

Configuration and Usage

Best Practices

  • Limit each service instance to 4–8 threads to balance throughput and resource usage.
  • Use multiple instances on different servers for large-scale or distributed processing.
  • Set 'Hours of Operation' to restrict processing to specific time windows if needed.
  • Assign queues thoughtfully to segment work and optimize resource allocation.
  • Regularly monitor service status, error counts, and logs for proactive maintenance.

Diagnostics and Monitoring

  • All errors, connection issues, and critical stops are logged to the Grooper event log and database.
  • The service tracks statistics for completed tasks, errors, and thread activity, supporting reporting and analysis.
  • The CriticalStop event is raised for unrecoverable errors, enabling alerting and automated remediation.
  • The ProgressText property provides a real-time summary of pending, completed, and errored tasks, as well as thread count.

Impact

  • The service is essential for automated batch processing in Grooper.
  • Misconfiguration may result in underutilization, resource contention, or missed processing windows.
  • Proper configuration ensures reliable, scalable, and efficient unattended processing for all supported Code Activities.

For more information, see the documentation for Task Processor, Processing Queue, Code Activity, and Batch Process.

Properties

NameTypeDescription
General
Service Settings
Notification