Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve "no job functions found" error #3051

Open
mattchenderson opened this issue Dec 19, 2023 · 0 comments
Open

Improve "no job functions found" error #3051

mattchenderson opened this issue Dec 19, 2023 · 0 comments

Comments

@mattchenderson
Copy link

The warning that is logged when no job functions are found provides a few different, non-exhaustive options for remediation:

startupLogger?.LogWarning($"No job functions found. Try making your job classes and methods public. {Resource.ExtensionInitializationMessage}");

<data name="ExtensionInitializationMessage" xml:space="preserve">
<value>If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).</value>
</data>

In some cases (such as Functions or when organization wrap WebJobs for multiple projects), it isn't actionable. This needs to be revised to provide clearer, better help. The system should log what extensions it did find. It should not provide specific code to be added, at least not in all cases, as the user may not control the extension registration directly, for example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant