Codeunit 8909 "Email Retry Impl."
System Application · System.Email
Across versions
- BC23-25not present
- BC26added
- BC27-30unchanged
Neighbourhood 2 connected objects and pages
System Application · System.Email · BC26-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| TableNo | Email Retry |
| Permissions | tabledata “Sent Email” = ri, tabledata “Email Outbox” = rimd, tabledata “Email Retry” = rimd, tabledata “Email Message” = r, tabledata “Email Error” = ri |
Procedures
CleanEmailRetryByMessageId(MessageId: Guid)(internal)CancelRetryByMessageId(MessageId: Guid): Boolean(internal)CleanEmailRetry(MessageId: Guid)(internal)CreateEmailRetry(var EmailOutbox: Record "Email Outbox")(internal)UpdateEmailRetryRecord(MessageId: Guid; RetryNo: Integer; Status: Enum "Email Status"; ErrorMessage: Text; DateQueued: DateTime; DateFailed: DateTime; DateSending: DateTime)(internal)
Relations
- runs on Table 8890 “Email Retry”
Called by
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 8888 “Email Dispatcher” (4 calls:
RetrySendEmail → CreateEmailRetry,SendEmail → CleanEmailRetry,SendEmail → CreateEmailRetry, …)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Email Retry Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.