[DOC] Blocking activities has incorrect code examples about elsa-core HOT 2 OPEN

1. The behavior you're observing is consistent with the purpose of the CreateBookmark() method. When you call context.CreateBookmark(), it indicates a point where the workflow should pause and wait for an external event to resume. If you place a Console.WriteLine after CreateBookmark(), it will execute immediately because the workflow has not yet been suspended. To suspend the workflow in the middle of an activity, you should ensure that CreateBookmark() is the last call in the activity's execution path that should run before pausing.

2. Regarding the RunAsync() method, it seems there might be a discrepancy between the documentation and the actual API. The documentation you're referring to might be outdated or incorrect. To resume a workflow, you typically need to provide a bookmark ID to the RunAsync() method. If the overload you're looking for doesn't exist, you may need to use a different method or a different overload of RunAsync() that is available in the version of Elsa you are using.

For the most accurate and up-to-date information on how to suspend and resume workflows, I recommend checking the latest official Elsa documentation or the source code directly. If the documentation is indeed outdated, you can open an issue on the Elsa GitHub repository or contact the maintainers to request an update.

For now, you can try using the WorkflowInstanceFilter to find the workflow instance and then use the RunWorkflowOptions to specify the bookmark ID when calling RunAsync(). Here's an example based on the information from the GitHub issues:

var options = new WorkflowInstanceFilter
{
    Id = InstanceId,
};
var workflowInstance = await _workflowInstanceStore.FindAsync(options);
var workflowState = workflowInstance.WorkflowState;
var bookmark = workflowState.Bookmarks.FirstOrDefault(b => /* your condition here */);
var runOptions = new RunWorkflowOptions { BookmarkId = bookmark?.Id };

var result = await _workflowRunner.RunAsync(workflow, runOptions);

Please note that the above code is just an example and may need to be adjusted based on the actual API and your specific use case.

This comment was generated by Glime.

from elsa-core.

Right, in that case the first point can be ignored (since it was mostly a question anyway).

The second point still stands and using the RunAsync method like in the example will run the entire workflow, not just resume it.

from elsa-core.