Docs
ERP Crystal
MFG
System Tools
Utilities
Queued Tasks & Background Process Monitor

Queued Tasks & Background Process Monitor

Queued Tasks & Background Process Monitor - User Guide

1. Introduction 🏁🕝

A high-performance ERP system often performs “heavy-duty” tasks like generating a years-long Financial Ledger, processing thousands of payslips simultaneously, or migrating balances between financial years. To ensure that your screen does not “freeze” while these calculations happen, the system uses a Queued Tasks module. It moves these long-running operations into a specialized background queue, allowing the ERP to continue working on other tasks while the final result is prepared.

ℹī¸

Purpose of this Utility:

  • Background Processing: Offload time-consuming calculations to the server so that the user interface remains responsive.
  • Task Status Visibility: Monitor whether a large report or bulk action is “Pending,” “In-Progress,” or “Completed.”
  • Failure Recovery: Identify if a technical interruption occurred and re-trigger tasks that couldn’t be completed.

This module is essential for Operation Managers, IT Support, and Data Accountants.

2. Key Operational Indicators 🚀

A. Real-Time Status Monitoring

The system labels every background task with a specific status:

  • Pending: The task is in the “Waiting Room” and will start as soon as server resources are available.
  • In-Progress: The engine is actively calculating data or generating documents.
  • Completed: The final result (e.g., an Excel report) is ready for download.
  • Failed: The task was interrupted (e.g., due to a data error).

B. Task Metadata

For every background job, the system records:

  • User Name: Who initiated the long-running operation.
  • Queue Date: The exact timestamp when the request was made.
  • Task Name: The specific activity being performed (e.g., “Financial Ledger Report (XL)”).
  • Notes: Any technical error messages or success summaries from the server.

3. The Lifecycle of a Queued Task 🛠ī¸

  1. Initiation: You request a large report (e.g., a Carry Forward). The system says, “This will take time; I’ve added it to the queue.”
  2. Tracking: You navigate to the Queued Tasks page to check the progress.
  3. Completion: Once the status changes to “Completed,” your result is either emailed to you or becomes available in the “Reports” repository.
  4. Re-Queue (If Needed): If a status shows “Failed,” you can re-trigger the original request after correcting any underlying data issues.

4. Understanding Global Indicators 📊

  • Task Name: The official title of the background activity.
  • Queue Status: The current lifecycle stage of the job.
  • Queue Date: The submission timestamp (dd-MMM-yy HH:mm).

5. Source Transactions 🔄

The queuing engine interacts with:

  1. System Task Queue Master: The high-performance database table that manages the “To-Do” list for the server.
  2. Asynchronous Jobs Engine: The specialized backend software that executes calculations without blocking your browser.
  3. Report Storage Repository: The secure directory where generated documents are held until they are delivered.

6. Best Practices / Tips 💡

  • The “Don’t Duplicate” Rule: If you see a task is “Pending” or “In-Progress,” there is no need to request the report again. Doing so will only create duplicate load on the server and potentially slow down your results.
  • Check the “Failed” Notes: If a task fails, always read the Notes column. It often contains specific instructions on why it failed (e.g., “Date Out of Range” or “Email Address Missing”).
  • System Admin Permissions: For high-trust tasks like the Carry Forward, check the queue regularly to ensure no critical background migrations have stalled.
  • Large-Scale Reporting: Especially during the financial year-end, use the Queued Task feature for any report spanning more than 6 months of data to ensure the most stable delivery.
Email Credentials & SMTP Gateway SetupSupport Request & Technical Ticketing