Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings Surfaces the daily ops questions a merchant or web agency lives with in Wrike: is the OAuth token still good, is our backlog drowning, are people overloaded, and (most importantly) are the findings we filed actually getting resolved or quietly dying in the queue?

What this audit checks

Authentication & access

  • OAuth2 access/refresh token still valid (auth on /api/v4/contacts?me=true)
  • Default space / folder exists and is writable
  • A writable workflow with Active + Completed custom statuses is available
  • Account rate-limit headroom > 30% (429 / Retry-After watch)

Backlog health

  • Open task count vs 30-day baseline (sudden growth = drowning signal)
  • Blocked / on-hold task count + change WoW
  • Oldest open task age (>90 days = backlog rot)
  • Unassigned tasks > 5 (empty responsibleIds - work nobody owns)
  • Backlog-by-importance skew (mostly Low = no one is grooming)

VortexIQ findings lifecycle (the stickiness test)

  • Abandoned findings - VortexIQ-created tasks, no status change >14d
  • Finding resolution rate over rolling 90d (target >75%)
  • Avg time-to-fix for resolved findings, by severity
  • Findings closed Cancelled without comment (silent dismissals)
  • Regression rate - findings that reopened after Completed

Team capacity

  • Responsibles with >10 active tasks (overload signal)
  • Responsibles with zero completed tasks in 14d (parked work)
  • Cycle time degradation > 25% week-over-week
  • Project scope-creep (tasks added after project start date)

Cross-connector signals

  • Critical findings from sibling connectors (shopify/bigcommerce/adobe/cybersource) older than 7 days with no Wrike task - coverage gap
  • Wrike tasks referencing decommissioned / archived integrations - stale work

Severity thresholds

SignalWarnCritical
vortexiq_findings_abandoned515
vortexiq_finding_resolution_rate7550
blocked_tickets38
unassigned_tickets520
oldest_open_ticket_age_days6090
cycle_time_change_pct2550
rate_limit_headroom_pct3010

Data sources

  • GET https://{host}/api/v4/contacts?me=true - Token + account info
  • GET https://{host}/api/v4/spaces - Default space access + writability check
  • GET https://{host}/api/v4/workflows - Custom-status → status_category mapping
  • GET https://{host}/api/v4/tasks - Backlog reads (open count, blocked, abandoned, by-assignee, throughput, etc.)
  • GET https://{host}/api/v4/folders - Project folders for sprint-equivalent progress + scope-creep
  • GET https://{host}/api/v4/folders/{folderId}/tasks - Tasks within a project folder for velocity history