Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Jon_Donker
Creator
Creator

Qlik Enterprise Manager - schedule question

Hi Team,

I am looking at migrating our QR schedules via pipelines for different environments.  When I export out the QR server via api and look at the schedules; I see the schedules are set up like this:

 

{
    "name": "DEV_S004_GCS_DLA",
    "command_id": 25,
    "schedule": "0 1 * * * *",
    "command_requests": {
        "cleanlogs_req": {
            "server": {},
            "task": {},
            "fts": {}
        },
        "logfilerollover_req": {},
        "execute_req": {
            "task": "",
            "operation": "EXECUTE_OPERATIONS_BOTH",
            "flags": "FRESH"
        },
        "stoptask_req": {
            "task": ""
        }
    },
    "task": "DEV_T222_DL_LENDING_DLA",
    "is_local_time": true
}

 

In the "schedule" section - it looks like a cron; but it has six variables instead of the expected five.  Can you please inform me what these different variables mean?

Labels (1)
1 Solution

Accepted Solutions
Jon_Donker
Creator
Creator
Author

Thanks Mark.

I worked it out after a bit of experimenting.  It is "Year" for the once off runs in Qlik Replicate.

 

Eg:

Jon_Donker_0-1766117306508.png

 

{
	"name":	"Test",
	"command_id":	25,
	"schedule":	"30 15 7 1 * 2026",
	"command_requests":	{
		"cleanlogs_req":	{
			"server":	{
			},
			"task":	{
			},
			"fts":	{
			}
		},
		"logfilerollover_req":	{
		},
		"execute_req":	{
			"task":	"",
			"operation":	"EXECUTE_OPERATIONS_BOTH",
			"flags":	"FRESH"
		},
		"stoptask_req":	{
			"task":	""
		}
	},
	"task":	"EIT_T002_OB_RFSB_ACCT_02",
	"enabled":	false
}

View solution in original post

3 Replies
marksouzacosta

Hi @Jon_Donker ,

Great question! I believe the schedule format you're seeing is a cron expression, but it uses the Quartz cron format rather than the standard Unix cron format. The key difference is that Quartz cron has 6 fields instead of 5, with seconds as the first field.

Here's the field breakdown:

Position Field Allowed Values 1 Seconds 0-59 2 Minutes 0-59 3 Hours 0-23 4 Day of month 1-31 5 Month 1-12 or JAN-DEC 6 Day of week 1-7 or SUN-SAT


So, for your example schedule "0 1 * * * *":

  • 0 = at second 0
  • 1 = at minute 1
  • * = every hour
  • * = every day of the month
  • * = every month
  • * = every day of the week

Full reference: 
https://help.qlik.com/en-US/compose/December2024/Content/ComposeDWDL/Main/DW/Cron%20Format%20and%20E...

Hope this helps!

 

Regards,

Mark Costa

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com

Jon_Donker
Creator
Creator
Author

Thanks Mark.

I worked it out after a bit of experimenting.  It is "Year" for the once off runs in Qlik Replicate.

 

Eg:

Jon_Donker_0-1766117306508.png

 

{
	"name":	"Test",
	"command_id":	25,
	"schedule":	"30 15 7 1 * 2026",
	"command_requests":	{
		"cleanlogs_req":	{
			"server":	{
			},
			"task":	{
			},
			"fts":	{
			}
		},
		"logfilerollover_req":	{
		},
		"execute_req":	{
			"task":	"",
			"operation":	"EXECUTE_OPERATIONS_BOTH",
			"flags":	"FRESH"
		},
		"stoptask_req":	{
			"task":	""
		}
	},
	"task":	"EIT_T002_OB_RFSB_ACCT_02",
	"enabled":	false
}
marksouzacosta

Great! Thanks for sharing @Jon_Donker .

I missed the right context of the question. It is on Qlik Replicate....... my bad.
I'll mark your answer as solution.

Thank you,

Mark Costa

Read more at Data Voyagers - datavoyagers.net
Follow me on my LinkedIn | Know IPC Global at ipc-global.com