AI translation

This page was translated from German with AI. If in doubt, the German original applies.

Error handling

Which errors the SDK reports, how to recognize them and how to react.

Error patterns at a glance

Symptom	Cause
RpcException, Unauthenticated	No refresh token or an invalidated one; also the symptom of a failed automatic refresh
RpcException, DeadlineExceeded	Time limit exceeded — on DIWASS paths usually a budget that is too tight, not a server error
OperationCanceledException	Cancellation via the CancellationToken
RpcException, InvalidArgument, “active provider not set”	Provider ID could not be resolved (0)
RpcException, InvalidArgument, “Input does not match the expected pattern”	UserId variant: more than four parts, usually special characters in the password
ArgumentOutOfRangeException on DefaultTimeout or WithTimeout	0 or a negative value other than NoTimeout
ArgumentOutOfRangeException on pollInterval	Poll interval below 1 second
InvalidOperationException, “DocXml is null”	Stage method on a handler without a loaded or created document
InvalidOperationException, “ZedalDocumentId is not set”	ReloadFromZedal / WaitForDiwassTransfer before the first save or send
KeyNotFoundException from LoadFromZedalBy…	Identifier not found in the ZEDAL data store — often it just hasn’t arrived yet
DiwassTransferFailedException	DIWASS rejected the transfer; details on the exception object
ArgumentException for DateTime parameters	DateTime.Kind is not Utc

Business rejections from DIWASS are not exceptions in this list — they come back as error codes in the result. See Error codes.