You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In HttpWorkflowsMiddleware class, ComputeBookmarkHash method
private string ComputeBookmarkHash(IServiceProvider serviceProvider, string path, string method)
{
var bookmarkPayload = new HttpEndpointBookmarkPayload(path, method);
var bookmarkHasher = serviceProvider.GetRequiredService();
var activityTypeName = ActivityTypeNameHelper.GenerateTypeName();
return bookmarkHasher.Hash(activityTypeName, bookmarkPayload);
}
ActivityTypeNameHelper.GenerateTypeName();
in this line it uses HttpEndpoint as a constant. But it records to the Bookmarks table with its customized name (in my case Elsa.HRVHTTPEndpoint) and creates the hash value in this way.
Therefore, it cannot find the record with the Hash value created with HttpEndpoint and the worklow does not continue.
Different type names work when creating(HRVHTTPEndpoint) a bookmark and consuming(HTTPEndpoint)
The text was updated successfully, but these errors were encountered:
In HttpWorkflowsMiddleware class, ComputeBookmarkHash method
private string ComputeBookmarkHash(IServiceProvider serviceProvider, string path, string method)
{
var bookmarkPayload = new HttpEndpointBookmarkPayload(path, method);
var bookmarkHasher = serviceProvider.GetRequiredService();
var activityTypeName = ActivityTypeNameHelper.GenerateTypeName();
return bookmarkHasher.Hash(activityTypeName, bookmarkPayload);
}
ActivityTypeNameHelper.GenerateTypeName();
in this line it uses HttpEndpoint as a constant. But it records to the Bookmarks table with its customized name (in my case Elsa.HRVHTTPEndpoint) and creates the hash value in this way.
Therefore, it cannot find the record with the Hash value created with HttpEndpoint and the worklow does not continue.
Different type names work when creating(HRVHTTPEndpoint) a bookmark and consuming(HTTPEndpoint)
The text was updated successfully, but these errors were encountered: