Suspend & Timeout functionality in WorkflowTemplates currently incompatible?

[BenjaminCaffrey]

Hi everyone! We use Argo Workflows and utilize a Suspend + Resume pattern. We successfully followed the documentation for Suspending and that worked well:

templates:
  ...
  - name: this-is-my-suspend-template
    suspend: {}

We suspend until we programmatically call argo resume. We want to combine it with a timeout and followed the Timeouts documentation to attempt to fail / abort a step created from this-is-my-suspend-template if it hasn't been programmatically resumed after a certain time:

templates:
  ...
  - name: this-is-my-suspend-template
    suspend: {}
    activeDeadlineSeconds: 10

This doesn't seem to work. Does this feel like an issue? Is there any documentation that states these two concepts are incompatible? Seems like there is a workaround here, I'm wondering if it's natively supported. Thank you!

[BenjaminCaffrey]

My understanding is that the duration argument will RESUME the workflow after the elapsed time, but I'm looking to fail / abort the workflow after the elapsed time.

[jswxstw]

activeDeadlineSeconds in suspend template will indeed not take effect.

argo-workflows/pkg/apis/workflow/v1alpha1/workflow_types.go

Lines 698 to 699 in 553c8ad

	// This field is only applicable to container and script templates.
	ActiveDeadlineSeconds *intstr.IntOrString `json:"activeDeadlineSeconds,omitempty" protobuf:"bytes,21,opt,name=activeDeadlineSeconds"`

[BenjaminCaffrey]

Thank you for confirming.