API Engine Release Notes - 1.21.2026040928.269642

Added

• Automation Run History
  API Automations now include full execution tracking, giving users visibility into every automation run,  when it started, how long it took, whether it succeeded, and what went wrong if it failed.

  • Run History records are created automatically each time an automation executes, capturing start/end times, duration, status, the triggering user, and the trigger source (Job Queue, Manual, or Event Subscriber).
  • API Message linking connects each API call made during an automation run back to its run history record. The API Message page now includes a "Run History Entry No." field with drilldown capability, and a FlowField on the run history tracks the total number of API calls per run.
  • Error capture records error messages and full call stacks when automation runs fail. The framework uses a Codeunit.Run() error boundary pattern that catches exceptions, logs them to run history, and allows the job queue to continue processing remaining automations in the group.
  • 30-day statistics FactBox displays on the Automation Card and Automation Group Card pages, surfacing Total Runs, Successful Runs, Failed Runs, and Success Rate at a glance.
  • Dedicated pages allow browsing run history from multiple entry points:
    • Run History List sorted by most recent, accessible from Automation Groups and Automations list pages.
    • Run History Card with full detail including error call stacks and associated detail lines
    • View All Run History action on the Automation Group Card for cross-automation visibility
  • Run status tracking uses a purpose-built enum with five states: Running, Success, Failed, Partial Success, and Cancelled.
  • Data retention is automatically configured through Business Central's Retention Policy framework with a default retention period of 6 months, compared to 1 month for API Messages.

   

 Updated

• "API Credential" Card Title

  • The API Credential Card page caption has been updated from singular "API Credential" to the plural "API Credentials" for consistency with the corresponding list page naming convention and accuracy.

Fixed

• BooleanToIntegerText Value Processing Always Returns 0

  • The BooleanToIntegerText value processing type returned '0' for all truthy input values. Two overloads in the Value Processing Utilities codeunit were affected:

    1. The mapping overload compared the data buffer value directly against the literal string 'true', causing values like 'True', 'Yes', and '1' to incorrectly return '0'.

    2. The variable overload used a lowercase comparison that handled case sensitivity but still failed for 'Yes'/'No' and '1'/'0' representations.

  • Both overloads now use Evaluate(Boolean, MyText), which correctly handles all standard Business Central boolean text representations.

  • Additionally, blank input now returns an empty string instead of incorrectly returning '0'.