​
Overview

​
Tool Name

process_scheduler_tools

​
Purpose

The process_scheduler_tools group is designed to automate processes by scheduling them to run at specific intervals or times. This helps optimize workflows and ensures tasks are executed consistently and without manual intervention.

​
Key Features & Functions

Manage Scheduling

Provides scheduling for processes, enabling them to trigger at predefined times or intervals.

Recurring & One-Time Execution

Supports flexible scheduling logic, including recurring tasks or one-time runs.

​
Input Parameters for Each Function

​
process_scheduler

Parameters
NameDefinitionFormat
actionSpecifies the action to perform: "CREATE", "UPDATE", "DELETE", "LIST", "TIME", or "HISTORY".String (required)
task_idUnique identifier for the process/task schedule (required for UPDATE or DELETE).String
task_detailsA JSON object containing schedule details (required for CREATE and UPDATE).JSON/Object
– process_name (string, required)Name of the process to run on this schedule.String
– primary_report_to_type (string, required)Entity type receiving task updates (e.g., SLACK_USER).String
– primary_report_to_id (string, required for CREATE)ID of the user/entity receiving notifications.String
– next_check_ts (string, required)Timestamp for next process execution (YYYY-MM-DD HH:MM:SS).String
– action_trigger_type (string, required)Schedule type (e.g., TIMER).String
– action_trigger_details (string, required)Describes how/when the task recurs or triggers.String
thread_id(Optional) Slack or other thread identifier for reporting.String
history_rows(Optional) Number of history rows to fetch with the HISTORY action.Integer
Genbot Tip Define clear action_trigger_details (e.g., "Repeats every hour") to ensure scheduling logic is easy to understand and maintain.

​
Use Cases

  1. Recurring Workflow Automation
    • Schedule a recurring data export process to run daily at 6:00 AM.
    • Example: Automating daily sales data imports to keep datasets updated.
  2. One-Time Triggered Processes
    • Set a one-time task for alpha testing new ETL pipelines.
    • Example: Running a batch process to clean outdated records on system go-live.
  3. Task Monitoring & History
    • Use the HISTORY action to see which jobs completed successfully or failed.
    • Example: Checking run history for weekly database backups to ensure reliability.
  4. Process Updates
    • Modify existing schedules when process timing changes or new configurations arise.
    • Example: Switching a weekly reporting task from Sunday to Monday at 9:00 AM.
IMPORTANT: Scheduling changes may disrupt dependent tasks; ensure you review downstream processes before modifying critical schedules.

​
Workflow/How It Works

  1. Step 1: Define New Schedules
    • Use process_scheduler with the CREATE action to specify process_name, next_check_ts, and recurrence details.
  2. Step 2: Monitor Scheduled Processes
    • List active schedules with the LIST action to review upcoming tasks or timings.
  3. Step 3: Update or Modify Schedules
    • Use UPDATE to adjust frequency, timing, or process details.
  4. Step 4: Remove Irrelevant Schedules
    • Invoke the DELETE action to clean up outdated or redundant processes.
  5. Step 5: Review History for Insights
    • Use HISTORY to audit how often tasks have run, including successes or failures.

​
Integration Relevance

  • Automated Testing: Combine with manage_tests_tools to run QA or test suites at set intervals.
  • Workflow Process Management: Works alongside process_manager_tools to define recurring automated tasks at the process level.
  • Task Dependencies: Complement project_manager_tools to schedule tasks respecting project timelines.

​
Configuration Details

  • Use unique task_id values to avoid conflicts among similarly named processes.
  • Always format next_check_ts as YYYY-MM-DD HH:MM:SS to align with system expectations.
  • Clearly document action_trigger_details for clarity on triggers (e.g., daily, weekly, monthly).
NOTE: Time zones can be crucial—make sure your scheduled tasks align with the relevant time zone to avoid confusion or unintended timings.

​
Limitations or Notes

  1. Time Zone Considerations
    • Scheduled times should match the environment’s or organization’s time zone, preventing offset errors.
  2. Manual Adjustments
    • Changing schedule details frequently can disrupt workflows or dependencies.
  3. Process Overlap
    • Stagger high-resource tasks to avoid performance bottlenecks if multiple processes run simultaneously.

​
Output

  • Scheduling Actions
    • Confirmation or error messages upon CREATE, UPDATE, DELETE actions.
  • Listing & Timing
    • LIST provides all active schedules; TIME may return current system time used for scheduling alignment.
  • History Retrieval
    • HISTORY yields run logs, indicating successes, failures, and timestamps.