BC Observatoryunofficial, made by waldo
codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 461 "Job Queue Cleanup Tasks"

Base Application · System.Threading

Open in Claude461.mdSource on GitHub

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Table 472 "Job Queue Entry" (relates to)Job Queue EntryCodeunit 456 "Job Queue Management" (calls, 3 links)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 · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Job Queue Entry

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.

  • Codeunit 456 “Job Queue Management” (3 calls: CleanupJQTasks → CheckAndRefreshCategoryRecoveryTasks, CleanupJQTasks → FindStaleJobsAndSetError, OnRun → UpdateRetriableFailedJobQueueLogEntry)

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 Cleanup Tasks"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources