What is this message "Breaking change analysis operation failed"?

Question

What is this message "Breaking change analysis operation failed"?

Andrew HB 341

Hi,

I have an Azure HTTP Triggered Function project that after a deployment raises the following warning in our logs. I cannot find anything about this on Stack Overflow and although nothing seems to be affected I would like to understand what the message means, also how to prevent it.

2020-05-21 14:03:44.778 +00:00 [Warning] Breaking change analysis operation failed
System.NotSupportedException: The invoked member is not supported in a dynamic assembly.
at System.Reflection.Emit.InternalAssemblyBuilder.get_CodeBase()
at Microsoft.Azure.WebJobs.Script.ChangeAnalysis.ChangeAnalysisService.LogBreakingChangeReport(CancellationToken cancellationToken) in D:\a\1\s\src\WebJobs.Script.WebHost\BreakingChangeAnalysis\ChangeAnalysisService.cs:line 140
at Microsoft.Azure.WebJobs.Script.ChangeAnalysis.ChangeAnalysisService.TryLogBreakingChangeReportAsync(CancellationToken cancellationToken) in D:\a\1\s\src\WebJobs.Script.WebHost\BreakingChangeAnalysis\ChangeAnalysisService.cs:line 103

Andrew HB 341 Reputation points

2020-05-22T11:02:39.277+00:00

Do Microsoft monitor this forum?
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-05-26T14:35:13.98+00:00

Hi @Andrew HB ,

We do indeed monitor these forums. I personally was lookup up your issue but didn't find anything definitive. Therefore, we'll need to take a closer look. Please email us at AzCommunity[at]microsoft[dot]com ATTN Ryan with your subscription id and Azure Function name enclosed so we can investigate.

Apologies again for not getting back to you sooner.
Andrew HB 341 Reputation points

2020-05-26T15:08:25.77+00:00

Hi Ryan, sorry didn't mean to sound impatient I was just checking I was in the right place.

I have noticed that I don't seem to get the issue on the Premium Plan it only occurs on the Consumption Plan we have running for our test box.

I'll email you my subscription number and the name of the service in question for your review.

Thanks again!

Andy
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-06-05T20:08:11.837+00:00

Hi @Andrew HB ,

Wanted to follow up with you to see if still needed help. Let me know.

Ryan
Andrew HB 341 Reputation points

2020-06-06T06:13:22.003+00:00

Hi Ryan,

I am still awaiting a response from the Microsoft Product Group, I seem to have raised a challenging issue!

I will report any resolution/outcome back here so it is available for other users in the future.

Regards,
Andy
Remus Dutulescu 1 Reputation point

2020-07-02T10:33:01.887+00:00

Hi Andrew,

Any resolution on this? I'm also experiencing this issue with a blob trigger function deployed in AKS
Quoc Nguyen 1 Reputation point

2020-08-27T09:44:00.563+00:00

I have the same problem
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-08-27T12:52:43.173+00:00

ChangeAnalysisService is a service used to identify any potential problems with code during an upgrade, e.g. new function runtime version. It should not have any impact on your code nor should it prevent your function app from being ran.

You can use the Diagnose and solve problems blade to confirm your function's invocations.
Lašček Ondrej 6 Reputation points

2020-09-17T06:38:10.41+00:00

Hi, same problem here. Did you solve this?
Andrew HB 341 Reputation points

2020-09-17T07:32:18.947+00:00

No sorry, the only response I got after about 4 weeks was the one you can read below from @Ryan Hill not a particularly useful response if I'm being honest!

I still get the issue, to replicate I simply republish my updated API from Visual Studio to the Azure Function and every time I make a call to the service from my app I get a log file emailed to me with this pesky warning within it!

There seems to be no plausible reason for the warning, I am not making any changes to the function runtime version during my deployment so it is still a complete mystery.

The only thing that surprises me is that more people aren't reporting it, I can only assume because they either do not have any form of sensible logging integrated within their apps or the logging they do have is configured not to report warnings.
Lašček Ondrej 6 Reputation points

2020-09-17T10:19:41.867+00:00

OK, so I've just got answer from azure support that "Primarily the service is for internal use and should have no impact on the customer's code." so I'll filter out those messages from our monitoring query...

Accepted answer

1 additional answer

Your answer

Andrew HB 341 Reputation points

2020-05-22T11:02:39.277+00:00

Do Microsoft monitor this forum?
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-05-26T14:35:13.98+00:00

Hi @Andrew HB ,

We do indeed monitor these forums. I personally was lookup up your issue but didn't find anything definitive. Therefore, we'll need to take a closer look. Please email us at AzCommunity[at]microsoft[dot]com ATTN Ryan with your subscription id and Azure Function name enclosed so we can investigate.

Apologies again for not getting back to you sooner.
Andrew HB 341 Reputation points

2020-05-26T15:08:25.77+00:00

Hi Ryan, sorry didn't mean to sound impatient I was just checking I was in the right place.

I have noticed that I don't seem to get the issue on the Premium Plan it only occurs on the Consumption Plan we have running for our test box.

I'll email you my subscription number and the name of the service in question for your review.

Thanks again!

Andy
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-06-05T20:08:11.837+00:00

Hi @Andrew HB ,

Wanted to follow up with you to see if still needed help. Let me know.

Ryan
Andrew HB 341 Reputation points

2020-06-06T06:13:22.003+00:00

Hi Ryan,

I am still awaiting a response from the Microsoft Product Group, I seem to have raised a challenging issue!

I will report any resolution/outcome back here so it is available for other users in the future.

Regards,
Andy
Remus Dutulescu 1 Reputation point

2020-07-02T10:33:01.887+00:00

Hi Andrew,

Any resolution on this? I'm also experiencing this issue with a blob trigger function deployed in AKS
Quoc Nguyen 1 Reputation point

2020-08-27T09:44:00.563+00:00

I have the same problem
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-08-27T12:52:43.173+00:00

ChangeAnalysisService is a service used to identify any potential problems with code during an upgrade, e.g. new function runtime version. It should not have any impact on your code nor should it prevent your function app from being ran.

You can use the Diagnose and solve problems blade to confirm your function's invocations.
Lašček Ondrej 6 Reputation points

2020-09-17T06:38:10.41+00:00

Hi, same problem here. Did you solve this?
Andrew HB 341 Reputation points

2020-09-17T07:32:18.947+00:00

No sorry, the only response I got after about 4 weeks was the one you can read below from @Ryan Hill not a particularly useful response if I'm being honest!

I still get the issue, to replicate I simply republish my updated API from Visual Studio to the Azure Function and every time I make a call to the service from my app I get a log file emailed to me with this pesky warning within it!

There seems to be no plausible reason for the warning, I am not making any changes to the function runtime version during my deployment so it is still a complete mystery.

The only thing that surprises me is that more people aren't reporting it, I can only assume because they either do not have any form of sensible logging integrated within their apps or the logging they do have is configured not to report warnings.
Lašček Ondrej 6 Reputation points

2020-09-17T10:19:41.867+00:00

OK, so I've just got answer from azure support that "Primarily the service is for internal use and should have no impact on the customer's code." so I'll filter out those messages from our monitoring query...

Answer 1

Ryan Hill 30,281 Microsoft Employee Moderator

Hi @Andrew HB ,

Apologies that my response wasn't clear before. The reason the warning is being raised is to identify any issues that potentially could arise during a platform upgrade. It is a log message that's used by the product team to be proactive in any potential issues. The message can fire during platform changes; therefore, there is not any code convention that can be implemented to change or prevent these messages from arising. It is however safe to ignore and you can filter the messages. The team does intend to change the log level so that it isn't obtrusive but there is no ETA on when the change will take place.

Regards,
Ryan

Andrew HB 341 Reputation points

2020-10-13T16:43:08.593+00:00

Hi @Ryan Hill can you confirm whether you would expect to see this message raised on every cold start, which is what seems to be happening, hence I don't get the error once after an upgrade it seems to occur every time the function app is fired up.

Anyway great news to see it's having the logging level downgraded, in the meantime I'm investigating Serilog to see if I can filter out that specific message :-)

Many thanks for the feedback.
Ryan Hill 30,281 Reputation points Microsoft Employee Moderator

2020-10-19T13:35:02.883+00:00

@Andrew HB I can confirm the message will be raised on every cold start. The fix for logging level change is https://github.com/Azure/azure-functions-host/pull/6757. You can follow this this PR to see when it makes it to a release branch. This Change Analysis Service is a utility that scans your usage of .NET APIs to make sure things don't break as Functions host is updated.

Answer 2

Andrew HB 341

Just returning to this as I continue to receive these warnings, I haven't accepted the answer from @Ryan Hill as it doesn't really tell me WHY the warning is being raised. Why is the Azure framework generating this warning and is there anyway that I can prevent the warning either by configuration or coding convention?

As others have suggested I to am going to look at filtering the warning message out of the log files as it really is quite annoying receiving these via our support desk every day.

Share via

What is this message "Breaking change analysis operation failed"?

1 additional answer

Your answer