Skip to content
Flowdence Flowdence Docs

Help and Support

For setup, troubleshooting, or incident assistance, contact Flowdence support at https://flowdence.io/support.

Security issues can be reported to security [at] flowdence.io. Privacy requests can be sent to privacy [at] flowdence.io.

When opening a support request, include:

  • Confluence site and space key.
  • Affected BoomiSight surface: configuration, dashboard tab, byline, macro, BoomiSight Specialist action, scheduled refresh, or export.
  • Approximate time and timezone.
  • Whether Verify Connection & Access reports available, limited, unavailable, or unsupported feature areas.
  • Screenshot of the visible warning or empty state, with credentials removed.

Do not include Boomi API tokens in support messages.

Common Checks

Section titled “Common Checks”
  • If all dashboards are unavailable, confirm the Boomi account ID, username, token, and Platform API access.
  • If execution data is empty, check whether the selected time window has recent executions and whether execution monitoring access is available.
  • If API Governance is partial, APIM metadata may be unavailable in the tenant. BoomiSight can still infer gateway indicators from runtime deployment data when core access is available.
  • If a macro cannot find a process, runtime, environment, or API, refresh the dashboard cache and then reopen the macro configuration dialog.
  • If page bylines are missing after an upgrade, open BoomiSight Configuration in that space and save the complete configuration once so the configured-space marker exists.
  • If Documentation Health has no results, run Scan Space Pages as a space admin. Refresh Cached Snapshot only reloads the previous result and does not scan pages.
  • If a current-page Rovo answer is unknown or not cached, confirm that the relevant BoomiSight macro or Boomi link exists on the page, then use the confirmed current-page refresh if appropriate. Do not reinterpret a current-space total as a page result.
  • If Process Property or XREF facts are missing, check the macro’s selected sources and freshness before refreshing. Raw values are intentionally never shown.
  • If a refresh is rate-limited, already in progress, or temporarily unavailable, keep the last good cache and retry after the displayed guidance rather than repeatedly starting refreshes.
  • If a compact macro appears too narrow, move it out of dense Confluence columns or use the detailed macro variant.