ISC: Workflows » cron » double execution

What problem are you observing?

Workflow was executed twice (in parallel), although it should have been executed only once per hour.

	"trigger": {
		"type": "SCHEDULED",
		"attributes": {
			"cronString": "0 * * * *",
			"frequency": "cronSchedule",
			"timeZone": "Europe/Berlin"
		}
	}

Here are the execution times side by side:

What is the correct behavior?

Obey the cron setting, make sure that the workflow is started once, and only once.

What product feature is this related to?

ISC Workflows

What are the steps to reproduce the issue?

  • Create a workflow with the trigger scheduled with the cron string 0 * * * *
  • Wait and monitor until the bug happens?

Do you have any other information about your environment that may help?

n/a.

Thank you for taking the time to report this @adamian . I noticed in your logs that this double execution only happened once. Have you seen any more occurrences of this double execution, or are you able to reliably reproduce it? If not, then your best path forward is to submit a support ticket so they can review your logs and see exactly what happened.

Hi @colin_mckibben,

Have you seen any more occurrences of this double execution, or are you able to reliably reproduce it?

My question would be, as SailPoint has access to the execution times (I assume), how often do you see this issue happening?
Is this working as designed, but maybe is this limitation not documented yet?

This is the first I’ve heard of it. A support case might be able to get to the bottom of this.

Maybe it is one in a billion chance, maybe people just don’t report bugs anymore.
Again, I think SailPoint has the code and data to check such issues, especially as ISC is a cloud solution, not an on-prem installation.

SailPoint Support needs 30 days just to confirm that “it is the expected behaviour that we are seeing right now.” (e.g. CS0309227), so I am very reluctant in investing the time.