The internal job id. It will be sued to track the job state in the database, so it must not change over time otherwise the job will be seen as a new one by the scheduler. That id, being technical, should only use valid characters such as [a-zA-Z0-9_-.]
The scheduling configuration for the job. For example a TimeSeries job can be configured to be hourly or daily, etc.
The job name as displayed in the UI.
The job description as displayed in the UI.
The job tags used to filter jobs in the UI.
The job side effect, representing the real job execution.
The job description as displayed in the UI.
The job side effect, representing the real job execution.
The internal job id.
The internal job id. It will be sued to track the job state in the database, so it must not change over time otherwise the job will be seen as a new one by the scheduler. That id, being technical, should only use valid characters such as [a-zA-Z0-9_-.]
The job name as displayed in the UI.
The scheduling configuration for the job.
The scheduling configuration for the job. For example a TimeSeries job can be configured to be hourly or daily, etc.
The job tags used to filter jobs in the UI.
The job SideEffect is the most important part as it represents the real job logic to execute. A job is defined for a given Scheduling, for example it can be a TimeSeries job. Jobs are also Workflow with a single vertice.
The kind of Scheduling used by this job.
The internal job id. It will be sued to track the job state in the database, so it must not change over time otherwise the job will be seen as a new one by the scheduler. That id, being technical, should only use valid characters such as [a-zA-Z0-9_-.]
The scheduling configuration for the job. For example a TimeSeries job can be configured to be hourly or daily, etc.
The job name as displayed in the UI.
The job description as displayed in the UI.
The job tags used to filter jobs in the UI.
The job side effect, representing the real job execution.