Root > Reference > All Types > TSendResult

Type TSendResult

Previous pageReturn to chapter overviewNext page   

Result kind for exception processing.







Code (Delphi)

TSendResult = (

srSent = S_OK,

srBugClosed = S_FALSE,

srNoExceptionInfo = S_NONE,

srRestart = E_RESTART,

srCancelled = E_CANCELLED,

srUnknownError = E_UNEXPECTED,

srUnsupportedSender = E_NOINTERFACE,

srConnectionError = E_CONNECTION_REFUSED,

srObsoleteVersion = E_OBSOLETE,

srInvalidLogin = E_LOGON_FAILED,

srInvalidSearch = E_INVALID_SEARCH,

srInvalidSelection = E_INVALID_SELECTION,

srInvalidRead = E_INVALID_READ,

srInvalidInsert = E_INVALID_INSERT,

srInvalidModify = E_INVALID_MODIFY





[SUCCESS] Exception was processed without errors. Sending method is set up, bug report was sent succcessfully and (most importantly) send method discovered that this exception is marked as "Fixed" in the target bug tracker.


[FAILURE] Exception processing was cancelled by user via dialog.


[FAILURE] Network connection error. This includes DNS errors.


[FAILURE] There was error when creating (opening) new case (ticket). For non-bug trackers methods this means error during content sending.


[FAILURE] There was error during log in stage. Most common reason is wrong login/password pair.


[FAILURE] There was error when modifying existing case (ticket). Applicable only for bug trackers.


[FAILURE] There was error during reading project or case options. Possible access denied error?


[FAILURE] There was error during project search. Reasons may be access denied or project was removed. Typically this is applicable only for bug trackers.


[FAILURE] There was error during selecting project (making project active). This value is used rarely, most often it's set by web-browser access methods.


[SUCCESS] There is no active exception. Nothing to do.


[FAILURE] Project version is obsolete. Bug reports are no longer required, submission is closed.


[FAILURE] Exception processing must be restarted. This value is typically used to switch between dialogs and handlers.


[SUCCESS] Exception was processed without errors. If sending is set up - then bug report was sent succcessfully.


[FAILURE] Common error code. It's used when no other code can be used.


[FAILURE] Unknown sender class. It's either wrong class name specified or sender class wasn't registered.



This value indicate result of exception's processing. There are 3 success codes (Send/BugClosed/NoExceptionInfo) and multiple error (failure) codes.


Success codes indicate that exception was processed successfully. "No exception to process/handle" is also considered as success.


Failure codes indicate that there was some kind of a error during exception processing. Restart and cancelling are considered as failures (however, often there are special cases to handle these codes).


UnknownError code is most general failure code. It's used when other codes can not be used.


See also

Send feedback... Build date: 2022-03-28
Last edited: 2022-03-28
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: