Slowing Dynamo - Flags cache is null

did anything change in your logs if you compare them with a text diff? (besides the time stamp :man_facepalming: )

also - I’d like to know if you tried to reproduce this in sandbox, with ALL packages removed including your own?

Are you behind a proxy in addition to firewall?

Sorry for not responding, had to catch up some deadlines.

To your questions:

  1. Logs are not changing with firewall changes, by IT department we are not behind proxy.
  2. I did try to run modified code in sandbox with:
    • No packages (even with all disables in preferences)
    • Without hardware acceleration
    • With turned off node preview

I did try one more thing, which was unplug the internet cable. This surprisingly helped and dynamo was running fast as racing horse (just like I need it), even when the “flags cache…” is still spamming in the log.

So it must be our firewall. Could you help me get list of things we should try to allow?

Still having the issue, but probably finaly found the problem. And the problem is "Microsoft edge webview2 " which spawns multiple instances when Dynamo opens.

When I run on PC where I enable it in firewall (personal PC at home) everything is ok (until it is updated and I need to allow it again). After that Dynamo works as expected.

Unfortunately that is not a solution at work, where because of security reasons we can’t allow it. I did whitelisted all adsk IP’s within “AdskLicensingSupportTool” and unfortunately it did not help with Dynamo.

I tryed a workaround… I manualy ended "Microsoft edge webview2 " in task manager under DynamoSandbox task … that didn’t help (node browser disapeared, dynamo still freezes after every run, “flag cache is null” still spaming).

Could you once more take a look at IPs your reaching to, so we can try to allow it selectivly? Allowing whole MsEdgeWebView2 is not an option but definitely it’s the cause!

Please help, it’s really frustrating to work with dynamo like that. 10 sec scripts can eventually run even 5 min because of the not responding Dynamo… that’s crazy and If you can’t help me It will probably make me leave Dynamo, which would make me really sad, cause I like the community, the connectivity, etc.

You’re (the Dynamo team) the only one who can help. @Michael_Kirschner2

Thanks for any additional advices to try

Webveiw2 is a requirement for Dynamo and other toolsets, and is the core ‘display’ component for a LOT of the Autodesk product offering (Revit’s homepage, multiple default add-ins, etc.). I recommend your security team review the impact that has (or will have if you’re still using old versions) in the larger context of the production environment.

That is true not only for Autodesk but for other brands like Adobe too.

But for ADSK and Adobe software it’s not a problem because we have IPs whitelisted which even WebView2 can use. But Dynamo must be using some other IPs than those of ADSK … and that’s where I’m searching your help.

We don’t have problem to allow Webview2 through known IPs after review of them, but to allow it without limitations.

The WebView2 components don’t require internet access to be used. You’re navigating a web page that is saved on disc, not pulled from an external address. My guess is that there is another component pulling data…

yeah, webView2 may be a red herring, the flags cache stuff is trying to interact with launch darkly, how did you come to the conclusion that WebView2 and the flags cache null messages were related?

From looking at the log again I see the following:

  1. Your machine fails to connect to Dynamo’s update bucket - it’s fine since it’s no longer used, but it fails to connect.
  2. your machine fails to connect to launch darkly. For some reason it looks like something is continually checking the FF connection - this could be rendering… or some other feature.
  3. From your last posts, I guess you also have some strange interaction with WebView2 which renders a bunch of features in Dynamo…

I actually think the webview 2 issue is probably the one causing slowdown as the interactions with the node library seem to be the ones in your video that cause actual performance issues.

some questions:

  1. What are you enabling / disabling in webview2 when you are configuring it?

  2. Can you try updating to a newer webview2 runtime?

  3. It definitely seems like perhaps you are on a misconfigured proxy or something like that - are you using VPN, a proxy etc? Have you tried without them?

  4. Can you please test in a 2.19 sandbox build from the Daily site.

  5. If you disable preview of geometry do you see the spammed feature flags message?

Without actually being able to reproduce the issue, which is probably going to be impossible since it seems to have to do with your exact office configuration or topology it’s going to be very hard to fix. If we get enough information to lead to ideas to try we can definitely send you custom builds. Looking forward to your response with more info.

Maybe a bit too late but solution found and published by autodesk support. If anybody runs into this topic just follow the steps in link and your dynamo will run smooth again-> https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Revit-2023-or-2024-freezes-regularly-after-a-script-has-been-run-in-Dynamo-for-Revit.html

Guys, the Solution works for RVT 2023 but unfortunately not with RVT 2024 … Is there another config or sth to update/ change, etc to be able work offline without dynamo slowing down?

@jacob.small @Michael_Kirschner2

Not that I know of - think you’re back to step one unfortunately. Best to open a support ticket via the accounts portal now. Ask them to keep both Michael and I informed as you progress.