Repository navigation
Orleans message delivery fails with ObjectDisposedException when DI scope is torn down mid-resolution #1540
Description
What is failing
When Orleans tries to forward a message to IMessageHubGrain.DeliverMessage (targeting the PlatformVersion hub), the PlacementDirectorResolver in the placement service calls into Autofac to resolve a placement director — but the DI LifetimeScope has already been disposed, producing an ObjectDisposedException that aborts the delivery.
Probable cause (high confidence)
A lifetime-scope race during shutdown or grain-deactivation cycling. The stack trace shows Orleans's PlacementDirectorResolver.GetPlacementDirector (in /_/src/Orleans.Runtime/Placement/PlacementDirectorResolver.cs:18) resolving via Autofac, whose LifetimeScope.ThrowDisposedException() fires because the scope was disposed before Orleans finished its message-addressing pipeline. This is a known class of race in Orleans+Autofac hosts when a request scope is disposed while in-flight resolutions are still outstanding.
Impact (low — ephemeral)
A single occurrence on one pod (memex-portal-deployment-75d78d7d95-svhr4), not repeated. The message was lost, but no broader cascade is evident. Likely coincided with a pod recycle or rolling update.
Where to look
PlacementDirectorResolver.csin Orleans.Runtime (upstream, line 18) — this is where the DI resolve is attempted.- The mesh's Autofac container registration for placement strategies — specifically how the
ILifetimeScopeis captured and whether it is a child scope that may outlive its parent. - The pod's lifecycle events around
2026-08-14T10:05:40Z— confirm whether a deployment or health-check recycle was in progress.
Evidence
| Fingerprint | ebf16fe17d683fb4 |
| Category | Orleans.Messaging |
| Severity | Error |
| Exception | System.ObjectDisposedException |
| Top frame | Autofac.Core.Lifetime.LifetimeScope.ThrowDisposedException() |
| Namespace | memex |
| Pods | memex-portal-deployment-75d78d7d95-svhr4 |
| Occurrences | 1 |
| First seen | 2026-08-14 10:05:40Z |
| Last seen | 2026-08-14 10:05:40Z |
Recent log lines
2026-08-14 10:05:40Z memex-portal-deployment-75d78d7d95-svhr4 fail: Orleans.Messaging[100071]
Failed to address message Request [S127.0.0.1:11111:145706738 sys.client/hosted-127.0.0.1:11111@145706738]->[ messagehub/Admin/PlatformVersion] MeshWeaver.Connection.Orleans.IMessageHubGrain.DeliverMessage(MeshWeaver.Messaging.IMessageDelivery) #656CB6C5D7FB2140[ForwardCount=1]
System.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed.
at Autofac.Core.Lifetime.LifetimeScope.ThrowDisposedException()
at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(ResolveRequest& request)
at Autofac.Core.Lifetime.LifetimeScope.Autofac.IComponentContext.ResolveComponent(ResolveRequest& request)
at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
at Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable`1 parameters)
at Autofac.ResolutionExtensions.ResolveKeyed(IComponentContext context, Object serviceKey, Type serviceType, IEnumerable`1 parameters)
at Autofac.ResolutionExtensions.ResolveKeyed(IComponentContext context, Object serviceKey, Type serviceType)
at Autofac.Extensions.DependencyInjection.AutofacServiceProvider.GetRequiredKeyedService(Type serviceType, Object serviceKey)
at Microsoft.Extensions.DependencyInjection.ServiceProviderKeyedServiceExtensions.GetRequiredKeyedService[T](IServiceProvider provider, Object serviceKey)
at Orleans.Runtime.Placement.PlacementDirectorResolver.GetPlacementDirector(PlacementStrategy placementStrategy) in /_/src/Orleans.Runtime/Placement/PlacementDirectorResolver.cs:line 18
at Orleans.Runtime.Placement.PlacementService.PlacementWorker.<>c__DisplayClass19_0.<<GetOrPlaceActivationAsync>g__InnerGetOrPlaceActivationAsync|0>d.MoveNext() in /_/src/Or…[truncated]
Opened automatically from Admin/_LogIncident/ebf16fe17d683fb4. Recurrences are folded into this issue rather than opening new ones.
Activity
systemorph-com commentedon Sep 17, 2026
Reopened — this fault is happening again.
Still occurring: 71 more since the last update (72 total).
memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnfRecent log lines
rbuergi commentedon Sep 18, 2026
Closing the family root too — its fix is in
origin/mainand core says so in source.src/MeshWeaver.Hosting/MeshTeardownHostedService.csnames this issue and its siblings explicitly:The repair is ordering, not a
catch: the drain moved toIHostedLifecycleService.StoppedAsync, which runs only after everyIHostedService.StopAsynchas returned — the web host's included — and still strictly before the host disposes the root provider. Draining inStopAsyncwas what tore the mesh down while Kestrel was still serving, so late requests re-entered the disposed root hub, re-createdAdmin/PlatformVersion, and re-subscribed Orleans streams on a stopped silo.Pinned by two tests that exist on disk today:
MeshHostBuilderTeardownOrderingTest.csandMeshTeardownRunsAfterEveryOtherHostedServiceTest.cs(plusHubScopeClosesAfterTeardownDrainsTest.cs,HubWatcherStopsAtTeardownStartTest.cs).All eight siblings in this family are now closed on that same evidence. Keeping the lowest number open as a "tracker" would track work that is finished, so this closes with them.
🚨 If the fault recurs, the bot reopens this issue with fresh evidence — that is the designed behaviour, and it is why closing a dormant incident is safe rather than optimistic. Two live faults from the same 2026-08-14 window are deliberately NOT covered here and stay open on their own tickets.
systemorph-com commentedon Sep 19, 2026
Reopened — this fault is happening again.
Still occurring: 1 more since the last update (73 total).
memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7fRecent log lines
rbuergi commentedon Sep 19, 2026
Why this family keeps reopening: "dormant" was measured across a period with no rolls
Working the backlog oldest-first. #1540, #1547, #1548 (and #1449, #1422 next door) were all closed on 2026-09-18 partly on dormancy — "15 days with no occurrence" — and all were reopened within a day. The reopens are correct, and it is worth saying so precisely, because the obvious reading is that the bot is misbehaving:
Every occurrence postdates its close, which is exactly what
Reopenrequires since #4577. Nothing here is a false reopen.🚨 What the dormancy actually measured. All five fired inside the 05:05–05:36Z window on 2026-09-19 — the roll storm. These are teardown faults: they fire when pods stop, and they are silent when nothing is stopping them. Fifteen quiet days meant fifteen days without a roll, not fifteen days of health. A rate measured under one regime does not survive ending it, and closing on that silence is what guaranteed the reopen.
The fix may not cover the path that is actually firing
MeshTeardownHostedServicenames this issue and its siblings as "all one root", and its drain is real:StoppedAsyncruns after everyStopAsyncand strictly before the root provider is disposed, so the mesh's in-flight paths are drained inside that window.But the line that reopened #1547 on 09-19 is not a mesh path:
That is Orleans' own grain-directory unregistration, on Orleans' own logger, resolving a service out of the container while deactivating. The mesh drain does not obviously reach it: it is not mesh in-flight work, and it runs on the silo's deactivation path rather than through any hosted service the drain waits on.
I am stating that as the open question rather than a conclusion — establishing whether Orleans' deactivation can outlive
StoppedAsyncneeds the silo lifecycle traced, not log lines.One confounder before anyone measures the current image
The pod that logged it,
memex-portal-deployment-65468bfccf-68g7f, was running at 05:04:58Z, and the image memex-cloud runs now (c25f86ae85b7) was built at 07:32Z the same day. So that occurrence says nothing about the current image — it is evidence about whatever that pod was running.merge-base --is-ancestor <teardown fix> c25f86ae85b7is what would settle whether the fix is even on the image, and the next roll is what would test it.Suggested handling: leave these open until a roll happens on an image provably carrying the teardown fix and produces no occurrence. Closing them on quiet between rolls will reopen them on the next roll, which is now the third time.
docs: rest the section on the three teardown faults, not five issues
rbuergi commentedon Sep 21, 2026
Cluster triage: this symptom has five distinct roots
Reviewed together with #1540 #1547 #1548 #3243 #3593 #2833 #2480 #5064 #4859 #5136 #4847 #4883 #4888 #4961 — every one of them reports
ObjectDisposedExceptionwithAutofac.Core.Lifetime.LifetimeScope.ThrowDisposedException()on top, or a teardown that did not finish. They are not one bug. The grouping, the discriminators and the evidence are committed asDoc/Architecture/DisposedScopeAndDyingHubs(added in #5159).Root R1 — the host container went down ahead of the mesh. Duplicate of #1548's root; already fixed.
This frame is upstream Orleans code (
PlacementDirectorResolver.GetPlacementDirector) resolving fromour Autofac scope, so there is nothing to patch at the frame — only the ordering around it.
MeshTeardownHostedService(src/MeshWeaver.Hosting/MeshTeardownHostedService.cs) names this issueby number in its own doc comment, together with #1541, #1542, #1544, #1545, #1546, #1547, #1548 and
#1560, as one root. It drains the mesh root hub in
StoppedAsync— after every other hostedservice's
StopAsynchas returned, the web host's included, and still strictly before the host disposesthe root provider.
StopAsyncwas the wrong hook: hosted services stop in reverse registration order,but
GenericWebHostServiceis registered byWebApplication.CreateBuilder, so Kestrel — and every liverequest and Blazor circuit — stops after anything
MeshHostApplicationBuilderregisters. Pinned byMeshHostBuilderTeardownOrderingTestandMeshTeardownRunsAfterEveryOtherHostedServiceTest.Evidence this is settled: last seen
2026-08-14 10:05:40Z, a single occurrence on one pod during arolling deploy; the fix landed 2026-09-15 and both portals have rolled since, with no recurrence.
🚨 One gap named rather than glossed: the ordering fix does not cover an aborted startup, where
Host.StartAsyncthrows andRunAsync'sfinallygoes straight toDisposeAsync()with the silo stillstopping. An R1-shaped fault on a pod that never finished booting is a different condition.
Closing as a duplicate of #1548, which is the survivor of the three in this cluster.
systemorph-com commentedon Sep 23, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 5 more since the last update (78 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7fRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Sep 23, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 62 more since the last update (140 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4jRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 5, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 4 more since the last update (144 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5rRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 5, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 696 more since the last update (840 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdvRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 5, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 1182 more since the last update (2022 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8qRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 6, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 432 more since the last update (2454 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8q,memex-portal-deployment-6cfcf78898-lsklhRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 7, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 1 more since the last update (2455 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8q,memex-portal-deployment-6cfcf78898-lsklh,memex-portal-deployment-5d74648df-ht6qxRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 7, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 1 more since the last update (2455 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8q,memex-portal-deployment-6cfcf78898-lsklh,memex-portal-deployment-5d74648df-ht6qxRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 13, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 3 more since the last update (2458 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8q,memex-portal-deployment-6cfcf78898-lsklh,memex-portal-deployment-5d74648df-ht6qx,memex-portal-deployment-68f94fffc4-mjl9v,memex-portal-deployment-f96cb5fd6-ckwqmRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Oct 22, 2026
Left closed — this ticket was closed as a DUPLICATE, which is a decision that the fault is tracked on another issue. Reopening it would discard that decision, so the occurrences below are recorded here instead — GitHub renders the cross-reference on the issue this was closed onto, where the analysis lives.
Still occurring: 1 more since the last update (2459 total).
memex-portal-deployment-6968cb99df-jrlb9,memex-portal-deployment-75d78d7d95-svhr4,memex-portal-deployment-7d89fc7947-s7s9k,memex-portal-deployment-7bcd994c74-vwn96,memex-portal-deployment-6dfbdb4d69-tzghx,memex-portal-deployment-6c74846cf8-kw26d,memex-portal-deployment-5d55558945-bh6rq,memex-portal-deployment-54f4c96b6b-8xnhx,memex-portal-deployment-54f4c96b6b-npxqc,memex-portal-deployment-7fd44b7695-xvwnf,memex-portal-deployment-65468bfccf-68g7f,memex-portal-deployment-786d86cf54-cfg4j,memex-portal-deployment-6485bffdff-cgd5r,memex-portal-deployment-848f664fd5-zzqll,memex-portal-deployment-848f664fd5-zqfrh,memex-portal-deployment-6cfcf78898-gkkdv,memex-portal-deployment-6cfcf78898-kss8q,memex-portal-deployment-6cfcf78898-lsklh,memex-portal-deployment-5d74648df-ht6qx,memex-portal-deployment-68f94fffc4-mjl9v,memex-portal-deployment-f96cb5fd6-ckwqm,memex-portal-deployment-c5dbd6d7b-56p5sRecent log lines
Re-addressed by the current identity function: this incident inherited
ebf16fe17d683fb4(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.