Bug: Elsa 2.0 Activity StartAt triggers a new workflow, although it is not a start trigger

I want to trigger a specific action when a ticket expires. For this I want to use StartAt and use the expiration date as the execution point.

I noticed that every time I start the program, the workflow is created. As I have seen, it is ignored that it is not a start trigger.

I use startAt in several places and so I defined it as follows.

var startAt = workflow.Add<StartAt>(startAt => startAt.Set(x => x.Instant, context => {
                var ticket = context.GetWorkflowContext<Ticket>();
                return Instant.FromDateTimeUtc(ticket.FollowupBy.Value.ToUniversalTime());
            }));

 workflow
                .WithContextType<Ticket>()
                .StartWith<EntityChangedTrigger>(.......

[sfmskywalker]

Indeed, that might be a nice solution. There’s already a way to build child graphs (used when creating composite activities), so perhaps this can be reused as-is or with some small tweaks.

[sfmskywalker]

Indeed, in this case the StartAt activity should not trigger the workflow when the application starts. I’ll try and see if I can reproduce this behavior.