Skip to content
Astera Technology

Give repeated action names separate step identities

Keep a sequence occurrence distinct from its action label.

Compare the rule with concrete cases

Original fictional sequence is check, adjust, check. Its occurrences are S1, S2 and S3. S1 has a pass result; S2 is complete; S3 has no result. Matching the word “check” must not reuse S1’s result for S3 or collapse the sequence to two actions.

Filled synthetic modelling cases
Step identityAction labelRecorded resultCompletion contribution
S1CheckPassedOne completed occurrence
S2AdjustCompleteOne completed occurrence
S3CheckAbsentStill incomplete
Download editable CSV ↓

Work through the distinction

Use stable occurrence IDs when repeated names are legitimate. Here completion means that each occurrence has its recorded execution result, not that every check passed. Name uniqueness would destroy the required second check.

How many of the three required occurrences are complete?

Show the worked answer

Two. S3 remains incomplete even though another occurrence with the same label passed.

Acceptance wording to adapt

Store results by step_occurrence_id. Permit S1 and S3 to share the label check, but require independent results for both. Sequence completion requires all three occurrence results.

Related resources