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
{{ message }}
This repository has been archived by the owner on Sep 8, 2021. It is now read-only.
Before it was possible to get schedule from config or even register a custom INameResolver to resolve "%xxx%" in runtime.
With the worker I'm getting "Microsoft.Azure.WebJobs.Host: Error indexing method 'xxx'. Microsoft.Azure.WebJobs.Host: '%xxx%' does not resolve to a value." before Main() is even called.
Well, the only reason we use "%xxx%" in Timer triggers is because there is no way to specify trigger time zone. Which is a degradation since Azure Functions V1 which did support it. Yes, I know I can run whole app in whatever time zone I want but it is not a valid solution because the rest of our code expects to run in UTC (which is a best practice btw).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before it was possible to get schedule from config or even register a custom INameResolver to resolve "%xxx%" in runtime.
With the worker I'm getting "Microsoft.Azure.WebJobs.Host: Error indexing method 'xxx'. Microsoft.Azure.WebJobs.Host: '%xxx%' does not resolve to a value." before Main() is even called.
Well, the only reason we use "%xxx%" in Timer triggers is because there is no way to specify trigger time zone. Which is a degradation since Azure Functions V1 which did support it. Yes, I know I can run whole app in whatever time zone I want but it is not a valid solution because the rest of our code expects to run in UTC (which is a best practice btw).
The text was updated successfully, but these errors were encountered: