TriggerX Docs
  • Introduction
    • What is TriggerX?
    • Key Features
  • Core Concepts
    • Architecture
    • Triggers in TriggerX
      • Time-Based Trigger
      • Event-Based Trigger
      • Condition-Based Trigger
    • Task Manager
    • Keepers
      • Keeper as Performer
      • Keeper as Attester
    • Aggregator
    • Network Monitoring
    • Contracts
      • AVS Governance
      • Attestation Center
  • Getting Started as Keepers
  • Monitoring And Analytics
    • Monitor Your Keeper
    • Monitor Your Job
  • Rewards
    • Keeper Rewards
    • Developer Rewards
    • Contributor Rewards
  • Fee Calculation
  • Guide
    • Templates
    • Usecases
  • Security Model
  • Community and Support
  • Appendices
    • Glossary
    • FAQ and Troubleshooting
    • Changelogs
  • References
  • Create Your First Job
    • Create Your First Time Based Job
    • Create Your First Event Based Job
Powered by GitBook
On this page
  • Overview
  • Core Objectives
  • Key Features
  • Operational Workflow
  • Integration with TriggerX Ecosystem
  1. Core Concepts

Task Manager

Overview

The Task Manager is the core orchestration engine within TriggerX, responsible for managing the lifecycle of automation jobs across decentralized networks. It ensures efficient scheduling, execution, and monitoring of tasks, providing a robust foundation for seamless automation in decentralized applications (dApps).

Core Objectives

The Task Manager is designed to:

  • Automate Job Scheduling: Facilitate seamless scheduling of tasks based on time, events, or specific conditions.

  • Optimize Resource Utilization: Monitor and manage system resources to prevent bottlenecks and ensure optimal performance.

  • Ensure Fault-Tolerant Execution: Implement mechanisms to handle task failures gracefully, including retries and failovers.

  • Support Distributed Execution: Coordinate task execution across multiple nodes in a decentralized network, ensuring scalability and resilience.

Key Features

Flexible Job Scheduling

The Task Manager supports diverse scheduling mechanisms:

  • Time-Based Triggers: Execute tasks at specified intervals or timestamps.

  • Event-Based Triggers: Initiate tasks in response to specific on-chain events.

  • Condition-Based Triggers: Trigger tasks when predefined conditions are met.

This flexibility allows developers to tailor automation workflows to specific application requirements.

Load Balancing and Resource Optimization

To maintain system efficiency:

  • Resource Monitoring: Continuously assess CPU, memory, and other system resources.

  • Dynamic Load Distribution: Allocate tasks to nodes based on current load, preventing overutilization and ensuring balanced workloads.

Fault Tolerance and Reliability

The Task Manager incorporates robust mechanisms to handle failures:

  • Retry Logic: Automatically reattempt failed tasks based on predefined policies.

  • Failover Support: Redirect tasks to alternative nodes in case of node failures, ensuring uninterrupted execution.

State Persistence

To ensure consistency and recoverability:

  • Periodic State Saving: Persist task states at regular intervals, enabling recovery from interruptions.

  • Audit Trails: Maintain logs of task executions, facilitating monitoring and debugging.

Scalability and Adaptability

Designed for growth:

  • Horizontal Scaling: Easily accommodate additional nodes to handle increased workloads.

  • Modular Architecture: Adapt to evolving requirements and integrate with various blockchain networks.

Operational Workflow

  1. Job Submission: Users define tasks through the TriggerX interface, specifying parameters such as execution criteria and resource requirements.

  2. Validation: The Task Manager verifies task parameters, ensuring they meet system criteria and resource availability.

  3. Scheduling: Validated tasks are scheduled based on their defined triggers and system load considerations.

  4. Execution and Monitoring: Assigned nodes execute tasks, with the Task Manager monitoring progress and handling any failures through retries or failovers.

  5. Completion and Logging: Upon successful execution, task outcomes are recorded, and relevant logs are maintained for transparency and auditing.

Integration with TriggerX Ecosystem

The Task Manager seamlessly integrates with other components of the TriggerX ecosystem:

  • Keeper Network: Coordinates with decentralized nodes responsible for task execution.

  • Smart Contract Layer: Interacts with smart contracts to initiate and manage on-chain operations.

  • User Interface: Provides users with real-time insights into task statuses and system performance.

PreviousCondition-Based TriggerNextKeepers

Last updated 1 month ago