API Reference
EmailStoreDiagnostic
Structured diagnostic emitted while reading a mailbox store.
Inheritance
- Object
- EmailStoreDiagnostic
Usage
Explore 26 API references to this type
This type appears in these public API surfaces even when no hand-authored example is attached directly to the page.
Returned or exposed by 26
- Property EmailArchiveAnalysisReport.Diagnostics
- Property EmailConversationGraph.Diagnostics
- Property EmailStoreAssociatedDataCatalog.Diagnostics
- Property EmailStoreAssociatedItem.Diagnostics
- Property EmailStoreContentSearchReport.Diagnostics
- Method EmailStoreDiagnostic.FromLimit
- Property EmailStoreExportEntry.Diagnostics
- Property EmailStoreExportReport.Diagnostics
- Property EmailStoreInspectionReport.Diagnostics
- Property EmailStoreMboxExportEntry.Diagnostics
- Property EmailStoreMboxExportReport.Diagnostics
- Property EmailStorePstCompactionPlan.Diagnostics
- Property EmailStorePstConversionReport.Diagnostics
- Property EmailStorePstMergeReport.Diagnostics
- Property EmailStorePstMutationPlan.Diagnostics
- Property EmailStorePstMutationReport.Diagnostics
- Property EmailStorePstSplitPartReport.Diagnostics
- Property EmailStorePstSplitPlan.Diagnostics
- Property EmailStorePstSplitReport.Diagnostics
- Property EmailStorePstWriteReport.Diagnostics
- Property EmailStoreReadResult.Diagnostics
- Property EmailStoreRecoveryExportReport.Diagnostics
- Property EmailStoreRecoveryReport.Diagnostics
- Property EmailStoreReminderQueue.Diagnostics
- Property EmailStoreSession.Diagnostics
- Property EmailStoreValidationReport.Diagnostics
Constructors
public EmailStoreDiagnostic(String code, String message, EmailStoreDiagnosticSeverity severity = Warning, String? location = null) #Creates a diagnostic.
Parameters
- code System.String
- message System.String
- severity OfficeIMO.Email.Store.EmailStoreDiagnosticSeverity = Warning
- location System.String? = null
public EmailStoreDiagnostic(String code, String message, EmailStoreDiagnosticSeverity severity, String? location, String? operation, Int64? byteOffset, String? limitName, Int64? actualValue, Int64? maximumValue, EmailDiagnosticDisposition disposition, EmailDataLossRisk dataLossRisk, String? suggestedAction, Boolean isRetryable = false) #Creates an actionable store diagnostic with machine-readable operation and recovery context.
Parameters
- code System.String
- message System.String
- severity OfficeIMO.Email.Store.EmailStoreDiagnosticSeverity
- location System.String?
- operation System.String?
- byteOffset System.Int64?
- limitName System.String?
- actualValue System.Int64?
- maximumValue System.Int64?
- disposition OfficeIMO.Email.EmailDiagnosticDisposition
- dataLossRisk OfficeIMO.Email.EmailDataLossRisk
- suggestedAction System.String?
- isRetryable System.Boolean = false
Methods
public static EmailStoreDiagnostic FromLimit(EmailStoreLimitExceededException exception, String operation, String? location = null, EmailDiagnosticDisposition disposition = Stopped, String code = "EMAIL_STORE_LIMIT_EXCEEDED") #EmailStoreDiagnosticCreates a non-sensitive actionable diagnostic for a bounded Store stop or skip.
Parameters
- exception OfficeIMO.Email.Store.EmailStoreLimitExceededException
- operation System.String
- location System.String? = null
- disposition OfficeIMO.Email.EmailDiagnosticDisposition = Stopped
- code System.String = "EMAIL_STORE_LIMIT_EXCEEDED"
Inherited Methods
public virtual Boolean Equals(Object? obj) #BooleanParameters
- obj Object?
Properties
public EmailStoreDiagnosticSeverity Severity { get; } #Diagnostic severity.
public String? Operation { get; } #Store operation that emitted the diagnostic.
public String? LimitName { get; } #Configured resource limit associated with the diagnostic.
public EmailDiagnosticDisposition Disposition { get; } #How processing continued after the condition.
public EmailDataLossRisk DataLossRisk { get; } #Whether the condition can omit or alter user data.
public String? SuggestedAction { get; } #Safe next action for an operator or calling application.
public Boolean IsRetryable { get; } #Whether retrying without changing source or policy can be useful.