Skip to content

Job Portal User Guide

Purpose

This document explains how to use the Job Portal in Domain Services Ops to monitor jobs, view logs, and manage automations. Example implementations of this portal include the Jobs-Minion and Automation menus.

Scope

This guide covers:

  • viewing the job list in Jobs-Minion
  • filtering and searching for jobs
  • opening job details and reading logs
  • performing Cancel Job or Remove Job actions when available
  • running and managing automations from the Automation menu

Prerequisites

Before using the portal, make sure that:

  • you already have an account and access rights to Domain Services Ops
  • the job and log services are available
  • you know the relevant environment or host group for the jobs you want to monitor

In the current configuration, the portal generally includes the following menus:

  • Jobs-Minion: job list for the wf-jobs-Minion connection
  • Automation: automation list that can create or trigger jobs
  • Accounts and User Groups: access administration menus

Using the Jobs-Minion Menu

Opening the job list

  1. Open the Jobs-Minion menu.
  2. The system will display the list of jobs within a specific time range.
  3. Job data will be refreshed automatically if auto refresh is configured.

Information displayed

Common columns on the job page include:

  • Task Id: the name of the task being executed
  • Status: job status, such as Pending, InProgress, Success, or Error
  • Host Id: the host processing the job
  • Duration: total job execution time
  • Delay: time gap between requested and started
  • Requested, Started, Finished: process timestamps
  • Tag: additional marker if available

Notes:

  • The date and time format follows the portal timezone, for example Asia/Jakarta
  • some columns may be hidden based on configuration

Filtering and searching

You can narrow down the job list in several ways:

  • use the filter row in the column header to search for specific values
  • use sorting on column headers to sort ascending or descending
  • use the grouping panel to group data
  • use the date filter in the toolbar to limit the search period
  • use the RESET FILTER button to clear active filters

Opening job details

  1. Click a job row in the table.
  2. The detail panel will open on the right side.
  3. This panel shows a job summary and the log area.

The detail information usually includes:

  • Task Id
  • Job Id
  • AccountId
  • HostId
  • Status
  • Duration
  • Delay
  • Requested
  • Started
  • Finished
  • Progress

Reading job logs

In the job detail panel:

  • the log area displays the related job logs
  • enable or disable Auto-refresh as needed
  • select the refresh interval, such as 3s, 5s, 10s, 30s, or 1m
  • use the refresh icon to reload logs manually

If logs are not available:

  • the system may display No logs available
  • this can happen because the job has not written any logs yet, the logs have not arrived yet, or the log source is unavailable

Job actions

Depending on the job status, several actions may be available:

  • Cancel Job: used when the job status is still InProgress
  • Remove Job: used when the job status is still Pending

Use these actions carefully because they affect running processes or queued jobs.

Understanding Job Status

Common statuses include:

  • Pending: the job has been created but has not started yet
  • InProgress: the job is currently running
  • Success: the job completed successfully
  • Error: the job failed or was stopped with an error
  • Removed: the job was removed from the queue

As an operational practice:

  • check Delay if a job waits too long before starting
  • check Duration if a job runs longer than normal
  • open the logs to identify the cause of an error

Using the Automation Menu

The Automation menu is used to view, create, update, and run automations that can generate jobs.

Information in the automation list

Common columns include:

  • Group
  • Name
  • Task Id
  • Job Id
  • Enabled
  • Host Group
  • Trigger Condition
  • Is Met
  • Last Requested Time
  • Current Status

Important values:

  • Enabled = Yes means the automation is active
  • Is Met indicates whether the trigger condition is currently satisfied
  • Job Id can be opened to jump to the related job page

Automation actions

In the Actions column, users can perform several actions:

  • Latest Log: view the latest automation log
  • Latest Met Log: view the latest log when the trigger condition was met
  • Trigger Now: run the job immediately without waiting for the normal trigger
  • View: open automation details
  • Edit: update the automation configuration
  • Delete: delete the automation
  • Enabled: enable or disable the automation

Viewing automation details

Use the View action to see:

  • automation identity such as Task Id, Full Name, Group, and Name
  • whether it is active or not
  • Priority, Host Group, Tag
  • Task Parameters
  • Trigger Operation
  • the list of triggers and each trigger's parameters

Creating a new automation

  1. Open the Automation menu.
  2. Click Create a new Automations.
  3. Fill in the information in the Automation tab.
  4. Add Task Parameters if needed.
  5. Open the Trigger tab.
  6. Add one or more triggers.
  7. Define the trigger condition.
  8. Click Create.

Notes:

  • an automation must have at least one trigger
  • you can use Clone an Automation to copy the configuration from another automation

Updating an automation

  1. In the desired automation row, select Edit.
  2. Update the data in the Automation or Trigger tab.
  3. Click Update.

Please note:

  • changing the isEnabled status on a trigger may show an additional confirmation
  • after deleting a trigger, the trigger condition may need to be updated again

Running Trigger Now

Use Trigger Now when you want to create a job directly from an automation without waiting for the normal condition.

Short flow:

  1. Select Trigger Now from the action menu.
  2. Review the job parameters that will be used.
  3. Click Submit Job.
  4. Open Jobs-Minion to monitor the execution result.

Enabling or disabling an automation

You can change automation status by using:

  • the Enabled switch in the action menu
  • the bulk action for multiple selected automations

Use this feature when you want to:

  • temporarily stop an automation
  • reactivate an automation after maintenance

Relationship Between Automation and Jobs-Minion

The Automation and Jobs-Minion menus are connected:

  • a triggered automation will generate a job
  • the Job Id in the automation list can be opened to see the related job details
  • the result of Trigger Now can be monitored directly in Jobs-Minion

Recommended workflow:

  1. create or update an automation
  2. run Trigger Now if a quick test is needed
  3. open Jobs-Minion
  4. check the job status
  5. open the logs to validate the result

Automation-to-job flow

Functionally, an automation is a rule that determines when a job should run. A job is the execution result of that automation.

The process works as follows:

  1. the automation is saved in an active or Enabled state
  2. the automation has one or more triggers
  3. the system evaluates the Trigger Condition
  4. if the trigger condition is satisfied, the automation requests job execution
  5. a new job appears in Jobs-Minion
  6. the job status changes throughout execution, such as Pending, InProgress, Success, or Error
  7. the job log can be opened from job details for further analysis

In other words:

  • Automation acts as the trigger or rule
  • Jobs-Minion acts as the place to monitor the execution result of that rule

Key relationship components

Several fields in automation are directly related to the resulting job:

  • Task Id: determines which task will run as a job
  • Host Group: helps determine the target host group for execution
  • Task Parameters: parameters sent when the job is created
  • Trigger Condition: the logical rule that determines when the automation runs
  • Current Status: the status of the latest job related to the automation
  • Last Requested Time: the last time the automation requested a job execution
  • Job Id: the identifier of the latest or related job

In practice:

  • if Task Id is wrong, the job may fail or run the wrong task
  • if Host Group is incorrect, the job may be routed to the wrong target
  • if Task Parameters are incomplete, the job may still be created but fail during execution
  • if the trigger is never met, then no job will be created

When a job is created from automation

A job can be created from automation in two main scenarios:

  • when the trigger condition is met normally
  • when a user runs the Trigger Now action

The difference is:

  • normal triggering depends on the automation trigger evaluation
  • Trigger Now is a manual execution that runs the job immediately

This is useful for two different needs:

  • routine automated operations
  • quick testing or manual validation by an operator

Meaning of Job Id in the automation list

Job Id on the automation page is the most direct link to the job page.

Its purpose is to:

  • show that the automation has already created or is currently associated with a job
  • provide a shortcut to open the related job details
  • help operators trace execution results without searching manually in the job list

Possible conditions:

  • if Job Id is filled in, there is usually a related job that can be traced
  • if Job Id is empty, there may be no recent related job reference yet, or the automation has not generated a job during that period

Meaning of Current Status and Last Requested Time

These two fields help you understand the relationship between an automation and its latest job:

  • Last Requested Time shows when the automation last requested a job to be created
  • Current Status shows the latest job status related to that automation

Example interpretations:

  • if Last Requested Time is recent but Current Status = Error, the automation successfully triggered a job, but the job failed
  • if Current Status = Success, the latest job from that automation completed successfully
  • if Last Requested Time is old or empty, the automation may not have been triggered again

Difference between automation logs and job logs

The portal provides two different log contexts, and it is important to distinguish them.

Latest Log or Latest Met Log in the automation menu is used to view logs related to the automation process itself, such as:

  • automation evaluation results
  • trigger information
  • evidence of whether the trigger condition was met or not
  • a trace of when the automation requested a job

Meanwhile, the log in the Jobs-Minion job detail is used to view the execution of the job itself, such as:

  • task execution steps
  • runtime errors
  • process progress
  • operational output from the job

How to read them:

  • if the automation does not trigger a job, check Latest Log or Latest Met Log
  • if the automation already triggered a job but the result failed, check the log in the job detail

Relationship between trigger condition and job creation

An automation has triggers and a Trigger Condition.

A trigger is a condition-checking component. The Trigger Condition is the logic that combines multiple triggers, for example:

  • all triggers must be satisfied
  • any one trigger is enough
  • a specific combination using logical operators

Its impact on job creation:

  • if the final condition evaluates to true, the automation can create a job
  • if the final condition evaluates to false, the job will not be created

Because of that:

  • the Is Met status helps operators understand why a job has not been created yet
  • disabled triggers may affect the result of the condition evaluation

Relationship between Trigger Now and Jobs-Minion

When a user clicks Trigger Now, the automation is used as a template for manual execution.

The job usually inherits:

  • Task Id
  • automation Group and Name as reference identity
  • Host Group
  • Task Parameters

After Submit Job:

  • the system creates a new job
  • the job appears in Jobs-Minion
  • the operator can open the job detail to monitor status and logs

This is commonly used for:

  • testing after editing an automation
  • parameter validation
  • rerunning a process without waiting for the natural trigger

End-to-end examples

Example 1, automation runs normally:

  1. the automation is in Enabled status
  2. trigger A and trigger B are evaluated
  3. the Trigger Condition is satisfied
  4. the system creates a job
  5. Last Requested Time on the automation is updated with the latest timestamp
  6. Current Status changes according to the job status
  7. Job Id can be opened in Jobs-Minion
  8. the operator checks the job log to confirm the result

Example 2, automation is active but no job appears:

  1. the automation exists and is Enabled
  2. the trigger condition is not yet satisfied
  3. no job is created
  4. Job Id may be empty or still refer to an older job
  5. the operator should check Latest Log or Latest Met Log
  6. the operator should review trigger status and the conditional formula

Example 3, using Trigger Now for testing:

  1. the operator opens the Automation menu
  2. the operator selects Trigger Now
  3. the operator reviews the parameters
  4. the operator clicks Submit Job
  5. a new job appears in Jobs-Minion
  6. the operator opens the job detail
  7. the operator monitors the status until completion
  8. the operator reads the logs to validate the result

How to investigate issues in the automation-job relationship

If the automation result does not match expectations, use this recommended check order:

  1. check whether the automation is Enabled
  2. check whether all important triggers are still active
  3. check whether the Trigger Condition is correct
  4. check Latest Log and Latest Met Log
  5. check whether Last Requested Time changes
  6. check whether a Job Id is created
  7. if Job Id exists, open the job detail in Jobs-Minion
  8. analyze the job status and job logs

Quick diagnosis pattern:

  • no new Job Id: the issue is usually in the trigger or automation evaluation
  • there is a Job Id, but the status is Error: the issue is usually in the job execution
  • there is a Job Id, but the status stays Pending too long: the issue may be in the queue or processing host
  • there is a Job Id, the status is Success, but the business result is wrong: check Task Parameters and job output

Usage Tips

  • use a narrower date filter to find jobs faster
  • check logs before performing Cancel Job or Remove Job
  • disable an automation first before making major changes
  • use clone automation for similar configurations
  • use Job Id as the main reference during investigation

Troubleshooting

Job does not appear

Check the following:

  • the date range in the filter
  • active column filters
  • whether the automation actually triggered a job
  • whether the selected data source connection matches the environment

Log is empty or does not appear

Possible causes:

  • the job has not generated logs yet
  • the log source is unavailable
  • the log token or connection is invalid
  • the job was just created and the logs have not been stored yet

Automation does not run

Check:

  • Enabled status
  • trigger condition
  • the status of each trigger
  • host group and task id
  • recent logs in Latest Log or Latest Met Log

Closing

Job Portal pages such as Jobs-Minion help the operations team monitor job execution in real time, while the Automation menu simplifies trigger management and automated execution. Use both together so monitoring, troubleshooting, and job validation can be done faster and more consistently.