microsoft/semantic-kernel · error · AggregateException

Plugin creation failed for {pluginName}

Error message

Plugin creation failed for {pluginName}

What it means

Error "Plugin creation failed for {pluginName}" thrown in microsoft/semantic-kernel.

Source

Thrown at dotnet/samples/Concepts/Plugins/ApiManifestBasedPlugins.cs:169

        var manifestLookupDirectory = Path.Combine(Directory.GetCurrentDirectory(), "..", "..", "..", "Resources", "Plugins", "ApiManifestPlugins");

        foreach (var pluginName in pluginNames)
        {
            try
            {
                KernelPlugin plugin =
                await kernel.ImportPluginFromApiManifestAsync(
                    pluginName,
                    Path.Combine(manifestLookupDirectory, pluginName, "apimanifest.json"),
                    apiManifestPluginParameters)
                    .ConfigureAwait(false);
                Console.WriteLine($">> {pluginName} is created.");
#pragma warning restore SKEXP0040
            }
            catch (Exception ex)
            {
                kernel.LoggerFactory.CreateLogger("Plugin Creation").LogError(ex, "Plugin creation failed. Message: {0}", ex.Message);
                throw new AggregateException($"Plugin creation failed for {pluginName}", ex);
            }
        }
    }
}

/// <summary>
/// Retrieves a token via the provided delegate and applies it to HTTP requests using the
/// "bearer" authentication scheme.
/// </summary>
public class BearerAuthenticationProviderWithCancellationToken(Func<Task<string>> bearerToken)
{
    private readonly Func<Task<string>> _bearerToken = bearerToken;

    /// <summary>
    /// Applies the token to the provided HTTP request message.
    /// </summary>
    /// <param name="request">The HTTP request message.</param>
    /// <param name="cancellationToken"></param>

View on GitHub (pinned to c028a0c7dc)

Solutions

1. Check that the plugin name matches an entry in the API manifest and that the manifest file exists and parses correctly.
2. Enable detailed logging around plugin creation to see the underlying parse or resolution error for the failing plugin.

When it happens

Trigger: Thrown at dotnet/samples/Concepts/Plugins/ApiManifestBasedPlugins.cs:169 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of microsoft/semantic-kernel@c028a0c7dc (2026-08-13). Data as JSON: /api/errors/f02028a18cd60647. Report an issue: GitHub.