codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 450 "Job Queue Error Handler"

Base Application · System.Threading

Across versions

  1. BC23present
  2. BC242 events changed
  3. BC251 events added, 1 events removed
  4. BC26unchanged
  5. BC272 events removed
  6. BC28-30unchanged

Neighbourhood 7 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 38507 "Job Queue External Events" (event subscribers)Job Queue External EventsCodeunit 40028 "Hybrid Scheduled Task Mgr" (event subscribers)Hybrid Scheduled Task MgrCodeunit 9803 "Job Queue Telemetry" (event subscribers)Job Queue TelemetryCodeunit 28 "Error Message Management" (calls, 3 links)Error Message ManagementCodeunit 29 "Error Message Handler" (calls)Error Message HandlerCodeunit 456 "Job Queue Management" (calls)Job Queue Management

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Threading · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Job Queue Entry
Permissions TableData “Job Queue Entry” = rimd, TableData “Job Queue Log Entry” = rm

Events published

Procedures

1 local procedures, no public ones.

Triggers

OnRun

Relations

Calls

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.

Called by

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: "Job Queue Error Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources