Skip to main content
Question

Access to ODX execution history / backlog in newer ODX versions

  • December 12, 2025
  • 1 reply
  • 5 views

Hi,

We are trying to access ODX execution history (backlog / queue / duration / errors) for log analytics purposes.

We understand from documentation and release notes that the local ODX backlog (Backlog.sqlite) has been removed / moved in newer ODX versions, and that execution metadata is now handled differently.

However, we are currently unable to locate where this information can be accessed programmatically.

Additionally, in the TimeXtender Portal, we do not see the menu option
Admin → Security / Permissions, so we are unable to:

  • verify roles/permissions

  • access or inspect the API for execution data

Could you please help clarify:

  1. Where ODX execution history (status, start/end time, duration, errors) is stored in newer ODX versions

  2. Whether this data is accessible via:

    • the TimeXtender Repository database, and if so, which tables/views are recommended

    • the TimeXtender API, and what permissions are required

  3. Why Admin → Security / Permissions is not visible in our portal, and what role is required to enable it

Our goal is to build log analytics / monitoring (history, duration, failures), similar to what was previously possible via the ODX backlog.

Thanks in advance for your help.

Best regards,
Eivind

1 reply

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • TimeXtender Xpert
  • December 12, 2025

Hi,

if you are running TimeXtender 20.10.x I don't think there is anything other than what is logged to Event Viewer. There the “portal” is https://portal.timextender.com . Note that with the release of TX Classic the ODX Server will go away, see: 

In TDI you can use the Meta Collections functionality to activate the collection from each Instance's cloud repository including Ingest (the successor of the ODX Server). In TDI the “portal” is found at https://app.timextender.com .

To get similar functionality going forward you would either need to move to Business Unit ingestion if you can live with SQL Server storage for raw data or migrate to TDI to be able to use the meta collections feature.