WorkatoSight 2.3.0 release notes

Released: 2026-08-08

Summary

WorkatoSight 2.3.0 introduces the WorkatoSight Specialist for Rovo, expands evidence-grounded architecture and governance answers, and improves the accuracy and resilience of cached Workato evidence.

New features

WorkatoSight Specialist for Rovo: Ask about the Workato solution documented on the current Confluence page or explicitly broaden the question to the cached Workato estate.
Curated architecture evidence: Review cached asset details, exact one- or two-hop relationships, Confluence page references, lifecycle context, runtime summaries, and API governance evidence without exposing raw cache records.
Deterministic readiness outcomes: Receive ordered insufficient-evidence, review-required, or ready-for-review outcomes based on explicit evidence rules rather than generated scores or inferred approval.
Asynchronous estate refresh: A Confluence space admin can explicitly confirm an estate refresh from the Specialist, receive a queued response promptly, and check the refresh status later.

Bug fixes and improvements

Completeness-safe refreshes: Complete, partial, failed, and stale-readable evidence are distinguished so an incomplete Workato response does not replace a previously complete snapshot.
Clearer runtime evidence: Runtime views separate Workato lifetime success and failure totals from the bounded representative Job sample shown below them.
Workato API browser links: API Collection and API Endpoint links now open their corresponding browser pages in the configured Workato workspace.
Safer page evidence: Credential-bearing and token-bearing URLs are omitted from page evidence instead of being exposed through summaries or Specialist answers.
More resilient Workato access: Refresh requests use bounded concurrency and retry temporary Workato throttling or service failures without creating unbounded request fan-out.

Scope changes

None. This release adds no new Atlassian scopes or permissions.

Admin action required

No action is required for existing dashboards, macros, bylines, or space configuration. To use the WorkatoSight Specialist, Atlassian Rovo must be available for the site and the agent may need organisation approval. Only a Confluence space admin can confirm an estate refresh from the Specialist.

Known limitations

Specialist answers use cached Workato evidence. Fresh Workato data requires an explicit admin-controlled refresh or an enabled licensed scheduled refresh.
Evidence-readiness outcomes support human review but do not approve architecture, assign ownership, or infer business impact.
Documentation Coverage remains a separate explicit Confluence scan and is not updated by a Workato estate refresh.
Specialist visibility for non-admin users depends on the site’s Atlassian Rovo and organisation-verification settings.