REST APIs: Retry-After header on rate limited responses
Rate limited requests to the Trackunit REST APIs now get a Retry-After header on the 429 Too Many Requests response. It gives the number of seconds to wait before sending the request again.
New features, APIs, and capabilities
View All TagsRate limited requests to the Trackunit REST APIs now get a Retry-After header on the 429 Too Many Requests response. It gives the number of seconds to wait before sending the request again.
@trackunit/react-table-helpers (from 3.0.0) no longer exports the custom-field column helpers. Those APIs now live in the new @trackunit/custom-field-table-helpers package. If your Iris App still imports them from react-table-helpers, bumping that dependency without running the migration is a compile failure. Apps that only use ExportTableButton are unaffected.
Run these two commands in the consuming repo after bumping the dependency:
npx nx g @trackunit/migrations:migrate
npx nx g @trackunit/migrations:run-migrations
CommandExecution.operationId on the public GraphQL API can now be null until the command is sent. CommandStatusType includes QUEUED and QUEUED_CANCELLED.
@trackunit/react-components 4.0.0 removes usePersistedState, useSearchParamSync, useCursorUrlSync, MAX_URL_LENGTH, the UrlPersistenceLocation type and Breadcrumb. They now live in the new package @trackunit/react-router-components (first published as 1.0.2), with no compatibility shim: if your code imports any of them, bumping to 4.0.0 without running the migration is a compile failure, not a deprecation warning. Repos that never used them are unaffected.
Run these two commands in the consuming repo:
npx nx g @trackunit/migrations:migrate
npx nx g @trackunit/migrations:run-migrations
Then re-install dependencies (npm install), because the migration adds @trackunit/react-router-components to your package.json.
Drawer callsites that clear their selected value on close (e.g. isOpen={Boolean(selectedRow)}) used to hand-roll a useRef/useState "last non-null value" snapshot just to keep the panel's content visible through the ~400ms exit slide — otherwise it blanked instantly. @trackunit/react-components and @trackunit/react-drawer now ship a shared primitive for this.
Your app can now request four new manifest scopes to check an account's connections and partnerships through the public GraphQL API: connection.view, connection.manage, partner.view, and partner.manage.
New Iris App workspaces now scaffold a databricks-unity-catalog skill under .agents/skills/, alongside the existing graphql, create-app, and other skills. It guides Claude, Cursor, and other coding agents through building a SERVERSIDE_API_EXTENSION that reads or writes customer-uploaded or app-owned tables in your IrisX Analytics Unity Catalog workspace — for data that Trackunit's GraphQL API can't serve.
Your extensions can now describe their own pages to Trackunit Manager's AI assistant. Add an
aiNavigation field to a manifest — a list of in-app routes, each with a path, a title, and a
description — and the assistant can take a user straight to the page inside your app that answers
their question instead of dropping them on its root.
This works today for every extension type that has a page a user can land on: Fleet, Admin, App Settings, Asset Home, Site Home, Customer Home, and Asset Events Actions. The field is opt-in and purely additive — apps that don't declare it behave exactly as before.
See Extension Point Types — AI navigation for the full reference: the manifest shape, both Tanstack Router styles, and in-app paths for entity-scoped extensions.
You can now inspect serverside function logs for your IrisX Apps directly in the Developer Console.
Open an app that includes Serverside API Extensions, select the Logs tab, then filter by date range and verbosity, search by message or function name, follow live entries when the range includes now, and open any row for full details.
See Viewing serverside function logs for the full guide.
The Telematics Device API now lets you roll back a previously executed configuration job. Rollback creates new configuration jobs that restore each device to the configuration it had before the original job ran.
Devices that have had their configuration changed since the original job (manually, by another job, or by automation) are excluded from rollback so the rollback never silently overwrites a newer change. A rollback request can produce more than one rollback job because devices are grouped by the previous configuration they shared.
Today, rollback is supported for CAN profile, Modbus profile, and Operating Mode changes. Other configurations the original job touched are excluded from the rollback's desired state — additional configurations will be announced as they become available.
➕ POST:
/v2/configuration-jobs/{id}/rollbacks