Help and Support

If You Need Help Fast

Collect these details before escalating:

• Confluence site URL
• affected space key
• affected tab/feature
• timeframe with timezone
• expected behavior vs actual behavior
• one screenshot or short video

Quick Triage by Symptom

Symptom: Connection test fails

1. Re-open Space settings -> MuleSight Configuration.
2. Verify client id, client secret, and org id values.
3. Re-run Test MuleSoft Connection.
4. Compare required scopes against your connected app.

Evidence references:

Symptom: Dashboard data is partial or missing

1. Open MuleSight Diagnostics and click Refresh Diagnostics.
2. Check Dataset Diagnostics for 403/timeout/other failed endpoint buckets.
3. Open Required Scopes and identify impacted scopes.

Evidence references:

Symptom: Security details are unclear

1. Open API Security Posture.
2. Click View security on the API row.
3. Review policies, tiers, and contracts in the modal.

Evidence reference:

Symptom: Ops pages are not updating

1. Check refresh interval and last sync in MuleSight Ops Dashboard.
2. Confirm watcher settings are saved if tagging is required.
3. Inspect Published Ops Pages and note empty-state vs linked pages.
4. Remember Refresh Ops Data reloads metadata only; it does not run the scheduler.

Evidence references:

Symptom: Rovo cannot answer endpoint method/path questions

1. Open a macro page using Exchange Endpoints display option.
2. Refresh the Endpoints macro once to seed endpoint cache.
3. Re-run the Rovo endpoint question in the same space context.

Evidence references:

Operational Rules to Remember

• Rovo behavior is space-context bound.
• Ops publishing is scheduler-driven and transition-driven.
• Diagnostics uses probe outcomes (full|partial|none) rather than token-claim parsing.
• This documentation pack covers single-space operation.