Cronjobs Model

Overview

The cronjobs table stores the configuration and execution details for scheduled cron jobs within a system. It includes fields to define the job's schedule, associated functions, task parameters, and metadata related to job execution.

Fields

Field	Type	Description	Required
id	string	Primary Key – Unique identifier for the cron job (UUID).	❌
cronId	string	Unique identifier for the cron job. This can be used for referencing or retrieving the job details.	✅
cronName	string	The name of the cron job, used for identification and easy reference.	✅
timeExpression	string	The cron time expression that defines the schedule for the job.	✅
expressionName	string	Name or description of the time expression, possibly for readability or specific use cases.	✅
taskFunctionData	object	Additional data related to the function that will be executed, such as parameters or configuration.	❌
userData	any	Data related to the user that triggered or owns the job, which could include user-specific parameters or configuration.	❌
taskFunction	string	The function or task that will be executed by the cron job.	❌
type	string	The type of the cron job (e.g., batch, API call, cleanup).	❌
status	string	The current status of the cron job (e.g., active, inactive, completed).	❌
timeZone	string	The time zone in which the cron job is scheduled to run.	❌
objectName	string	The name of the object associated with the cron job (e.g., "backup", "reporting").	✅
buildType	string	Type or version of the build the cron job belongs to (if applicable).	❌
package_type	string	The type of package or deployment the cron job is associated with.	❌
objectId	string	Unique identifier for the object associated with the cron job.	❌
parentProvider	string	The parent provider associated with the cron job (e.g., cloud provider, service).	❌
provider	string	The provider that will execute the cron job (e.g., server name, cloud service).	❌
customInputs	string	Custom input parameters for the cron job, which may modify its behavior.	❌
dataPackId	string	ID for the associated data pack, used if the cron job works with data packs.	❌
application_id	string	The ID of the application associated with the cron job.	❌
org_id	string	The organization ID associated with the cron job.	❌
sites_id	string	The site ID associated with the cron job.	❌
scheduler_type	string	The type of scheduler (e.g., internal, external, cron-based).	❌
isDebugEnabled	boolean	Whether debugging is enabled for the cron job (0 = disabled, 1 = enabled).	❌
created_at	date	Timestamp when the cron job was created.	❌
modified_at	date	Timestamp when the cron job was last modified.	❌
job_type	any	Description or type of job to be executed (e.g., "backup", "data sync").	❌
workflow_action_id	any	ID for the workflow action associated with the cron job.	❌

Relationships

• Belongsto Unknown
• Belongsto Unknown

Sample JSON

{
  "id": "example_value",
  "cronId": "example_value",
  "cronName": "example_value",
  "timeExpression": "example_value",
  "expressionName": "example_value",
  "taskFunctionData": "example_value",
  "userData": "example_value",
  "taskFunction": "example_value",
  "type": "example_value",
  "status": "example_value",
  "timeZone": "example_value",
  "objectName": "example_value",
  "buildType": "example_value",
  "package_type": "example_value",
  "objectId": "example_value",
  "parentProvider": "example_value",
  "provider": "example_value",
  "customInputs": "example_value",
  "dataPackId": "example_value",
  "application_id": "example_value",
  "org_id": "example_value",
  "sites_id": "example_value",
  "scheduler_type": "example_value",
  "isDebugEnabled": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "job_type": "example_value",
  "workflow_action_id": "example_value"
}