Recurring task management (GESABA) is a great feature. We can set up tasks to run automatically after hours or on some other predetermined schedule. This means no dialing in after hours to execute the tasks. No kicking yourself because you forgot to run the Stock Accounting interface yet again.

The only problem with not having to manually run the functions is: out of sight, out of mind. We still need to regularly monitor that the recurring tasks are not just recurring, but also finishing successfully.

Where do we do this and what should we be looking for? Head to Query Management (AREQUETE). To start, check out the Status for each Task Code.  For each line, you can click the action card and select Parameters to see which ones were used or Log to review the activity or errors generated by the running of the tasks.

 Here are the definitions of the Status codes with some tips on what to look for:

• Standby: the request has not yet been started.
  • Have these tasks been sitting there for a long time?
  • Are there multiples of the same task waiting in line?
• In progress: the request is in the process of being executed.
  • Are the tasks taking longer than usual?
• Finished: the request has finished without errors.
  • Even though there were no errors, check out what was generated by the running of the task.
  • If nothing was generated, check the dates, sites or other parameters that were used by function
    • Click the lines’ action card and select Parameters which will show you the setting for that run.
    • To change them for future executions, click Parameters under Recurring task management (GESABA).
• Aborted: the request was interrupted.
  • Why was it stopped and do I need to get this task restarted or rescheduled?
• Error: the task has terminated on an error.
  • Review the Log as soon as possible.
  • It is easier to deal with an error while the transactions are fresh in everyone’s minds.
  • Resolving the errors will speed up the processing as the program doesn’t have to keep going over these problem transactions.
  • Check the Sage Knowledgebase for assistance in resolving these errors.
• Held: the request is part of a group in the process of execution or it is blocked manually by an interruption.
  • Is this in process to run or do I have an interruption to investigate?
• Kill: A user has requested the termination of the request.
  • Why was it killed and do I need to reschedule this task?
• Immediate: the task has been submitted for immediate processing (via the intermediary of a file)
• Warning: the task ended on a non-blocking error code (GERRBATCH variable<100).
  • Review the Log to determine the origin of the warning.