| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Adds resilient workflow telemetry serialization so unsupported payloads fall back without disrupting execution.
Changes:
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| WorkflowTelemetryContext.cs | Adds telemetry serialization fallback. |
| ObservabilityTests.cs | Tests fallback behavior and workflow continuity. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
There was a problem hiding this comment.
Completed passes: 5 | Result: No high-severity findings
Scope: full PR (1 commit(s)): 7a45235d304e
Sorry, something went wrong.
There was a problem hiding this comment.
Completed passes: 5 | Result: No high-severity findings
Scope: 1 net-new commit(s): 1ca94adcb18d
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description & Review Guide
Workflow telemetry now safely falls back to an [Unserializable: ...] representation when sensitive payload serialization fails, without disrupting execution or altering the message stream. Adds regression coverage for unsupported AIContent, executor telemetry, AOT, and arbitrary serialization exceptions.
CodeInterpreterToolCallContent that was mentioned in the issue is now supported by current MEAI serialization, but the underlying telemetry failure remained for unsupported or custom content types. This change safely falls back to [Unserializable: ...] without failing workflow execution or altering the message stream.
Fixes #5066
Contribution Checklist