Skip to main content
Card class: Hero • Category: Project Management
Findings sat in the backlog with no status change for two weeks, these are the ones losing money silently.

​
At a glance

Open Vortex IQ-tagged Wrike tasks with no field change in 14+ days. Wrike is mid-market-to-enterprise PM software with strong agency / cross-functional support; common in marketing-led teams that need request-management workflows. The abandoned bucket here represents Vortex IQ findings filed into Wrike folders / projects but never picked up by the team. On Wrike-using merchants this card is the operational-discipline trip-wire; the parallel vortexiq_findings_open card sizes the queue, this card detects health.
What it countsOpen Wrike tasks where the custom field vortexiq_finding_id is set AND status is in an unresolved category AND updatedDate is older than 14 days.
What counts as movementAny of: status change, assignee change, priority change, due-date change, custom-field edit, comment posted, sub-task added, attachment added. Wrike tracks updatedDate on any task-level field change.
Project / board scopeAll Wrike folders / projects tagged vortex_iq_outbound in connector setup. The card aggregates across the entire connected Wrike account; multi-account merchants (rare) see a blended count by default.
Status filterWrike’s status categories: Active, Completed, Deferred, Cancelled. The card includes Active and Deferred (Deferred is a soft-defer that the team explicitly chose, not a passive abandonment); excludes Completed and Cancelled (terminal).
Issue type filterAll Vortex IQ-tagged tasks included regardless of Wrike task type. Sub-labels via Wrike’s Tags do not filter the count.
Resolution countsN/A; abandonment is about the open population only.
API endpointGET /tasks?customFields=[{"id":"vortexiq_finding_id","value":""}]&status=Active,Deferred&updatedDate=<{ISO_14d_ago} paginated via Wrike’s nextPageToken. The 14-day staleness clock evaluates on every webhook event and on a 5-minute scheduled refresh.
Time windowRT
Alert trigger>5 warn, >15 critical. Marketing-led Wrike teams often tune up to >10 warn because their cycle time is naturally slower than engineering teams.
Sentiment keyThreshold-based, {warn: 5, critical: 15}.
Time zoneWrike’s updatedDate is ISO-8601 UTC; the 14-day cutoff aligns to UTC.
Wrike Work Intelligence interactionWrike’s AI features can suggest assignees and statuses; accepted suggestions count as movement. Suggestions left unaccepted do NOT count.
Rolesowner, operations

​
Calculation

Calculated automatically from your Wrike (API) data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK 40-person mid-market homewares brand running Wrike Business across marketing, creative, and ops teams. Three Wrike folders connected (Marketing Operations, Creative Studio, Customer Operations). Snapshot taken on 02 May 26 at 12:45 BST.
Wrike folderOpen Vortex IQ findingsAbandoned (>14d no movement)Notes
Marketing Operations176Mostly meta-description regressions on the Easter campaign collection pages; assigned to a marketing ops lead on PTO.
Creative Studio93Image alt-text and structured-data findings; awaiting creative review board approval.
Customer Operations72Returns-policy URL drift; assigned to a CX lead but never picked up.
Total open3311At warn (>5), close to critical (>15).
Abandoned count       11
Warn threshold         5  (>5 warn)
Critical threshold    15  (>15 critical)
Status                warn (close to critical)
30D average abandoned  6
Delta vs 30D avg     +83%
What the merchant should read into this:
  1. Marketing Operations cluster has a single root cause. Six findings stagnant since the marketing ops lead went on PTO. The fix is reassignment, not hiring. Open Wrike’s Workload View and confirm; reassign to another marketing lead today.
  2. Creative Studio findings are blocked by review board, not abandoned per se. Three findings awaiting creative-review-board approval is not abandonment in spirit; the team is waiting on a process. The card flags them because Wrike’s data model does not distinguish “blocked” from “abandoned”. Add a Wrike custom status Awaiting Approval and exclude it from this card via connector configuration if your team uses formal approval gates.
  3. Customer Operations returns-policy URL drift is highest-revenue-risk. Returns-policy mismatches are conversion killers. Two findings stagnant for 18 days could be costing more revenue per week than the team realises. Triage today.
  4. Pair with wri_vortexiq_findings_open and wri_assignee_load. A growing open count is acceptable if the team is closing fast enough; abandoned-rate spike alongside growing open is the real warning sign.
  5. Use Wrike Workload View to surface concentration. Wrike’s Workload View shows tasks per assignee in time-series; combine with the abandoned filter to identify which assignees own most of the abandoned bucket. Most accounts find one or two assignees concentrate 50%+ of abandoned findings.
  6. Right action: weekly 30-minute “abandoned review”. With Wrike’s mid-market team profile, this works best as a Monday-morning 30-minute meeting with one ops lead. For each abandoned finding: complete (Completed), defer with reason (Deferred), reassign, or escalate. We see Wrike merchants close 30 to 50% of abandoned findings on this triage.

​
Sibling cards merchants should reference together

CardWhy pair it with Abandoned FindingsWhat the combination tells you
VortexIQ Findings OpenAbandoned is a subset of open. The ratio is the steadier read.Abandoned ÷ Open above 30% on Wrike = the queue is stagnating.
Finding Resolution Rate (90d)Resolution rate drops first; abandoned count rises second.The textbook capacity-collapse sequence.
Tasks by Assignee (Workload View)Tells you whether abandonment concentrates on one person.If 70% of abandoned findings sit on one assignee, the fix is reassignment.
Avg Time-to-FixCycle-time peer.Time-to-fix rising AND abandoned rising = team starting then stalling.
Project / Folder ThroughputThe team-velocity signal.Throughput flat + abandoned rising = findings being filed but not planned in.
Datadog Health ScoreIndependent peer for technical findings.Datadog elevated + abandoned rising on technical cards = engineering firefighting + audit work falling behind.
Shopify / BigCommerce Refund RateDownstream cost metric.Abandoned on returns / refund-flow drives refund rate up over a 4 to 8 week window.
Customer Service SentimentNPS-side outcome.Sustained abandoned predicts CSAT drop within a quarter.

​
Reconciling against the vendor’s own dashboard

Where to look in Wrike’s own UI:
Wrike app, open each folder tagged vortex_iq_outbound and use Wrike’s filter language to build the query: Custom Field: vortexiq_finding_id is set AND Status: Active OR Deferred AND Last Modified < 14 days ago. Save the filter as a Pinned View for the team. Reports on Business / Enterprise plans can build a Workload Report or Project Health Report scoped to the same filter for trend visibility. Dashboards can pin the saved filter as a tile.
Wrike does not ship a built-in “abandoned” view; this card is closest to the saved-filter pattern Wrike users already know. Why our number may legitimately differ from a saved Wrike view:
ReasonDirectionWhy
Time zoneNone expectedBoth Wrike and the card use UTC for updatedDate; gap is rare.
Status-category semanticsEitherThe card includes Active and Deferred; some saved Wrike filters include only Active. The choice depends on whether your team uses Deferred as “explicitly chosen wait” (in which case the card’s inclusion overcounts) or as “we’ll get to this eventually” (in which case the card’s inclusion is correct).
Custom-field deletionOurs lowerIf vortexiq_finding_id is cleared from a task, the task drops out of the count even though it is still abandoned.
Cross-folder aggregationEitherCard aggregates across all vortex_iq_outbound folders; Wrike’s saved filter typically scopes to one.
Sub-task countingOurs lowerVortex IQ creates findings as parent tasks. Untouched sub-tasks beneath a parent do not separately count; only the parent.
Wrike Work Intelligence movementSame in bothAI accepted suggestions update updatedDate; both views see this. Unaccepted AI suggestions do not update.
Webhook delayUp to 60s staleA movement event from the last minute may not have reached the card.
API rate-limit lagUp to 30s stale during peakWrike rate-limits at 100 requests/minute on most plans.
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
datadog.dd_incidents_activeIndependent. Datadog tracks live engineering incidents; Wrike tracks the audit-side remediation.Both elevated = engineering firefighting + audit work piling up.
shopify.refund_rateInverse correlation; abandoned on returns / refund-flow drives refund rate over a 4 to 8 week window.Abandoned on cosmetic findings only = no refund correlation.
shopify.customer_service_sentimentInverse correlation; 2 to 4 week lag.Sustained abandoned predicts CSAT drop.

​
Known limitations / merchant FAQs

Wrike shows my task was modified yesterday but the card says abandoned. What is wrong? Almost always one of two things. (1) The “modification” was a Wrike Work Intelligence AI suggestion shown but not accepted; the card treats only accepted suggestions as movement. Open the task and check the activity feed for an explicit human action in the last 14 days. (2) Webhook delay: an edit from the last 5 minutes may not have reached the card. What counts as movement? Any of: status change, assignee change, priority change, due-date change, custom-field edit, comment posted, sub-task added, attachment added. Renaming the task or editing the description also counts. Work Intelligence accepted suggestions count; unaccepted suggestions do not. Wrike’s Deferred status counts as open. Why? Because Deferred is a soft-defer; the team may have explicitly chosen to defer the task, but if it sits in Deferred for 14+ days without movement, it is functionally abandoned. If your team uses Deferred as “explicitly waiting on a known event” (e.g. waiting on a vendor response with a known return date), build a Wrike custom status like Awaiting Vendor and exclude it from this card via connector configuration. The 14-day window feels arbitrary. Can we tune it? Yes, in Settings, Connectors, Wrike, Abandonment threshold (days). Default is 14 days. Marketing-led Wrike teams often tune up to 21 days because their cycle time is naturally slower than engineering teams; engineering-led teams tune down to 10 days. Multi-folder: my account spans multiple Wrike folders. The count looks alarming. Open the per-folder stack panel from the connector drawer to see which folder drives the abandoned count. Most multi-folder merchants find the abandoned bucket concentrates in one or two folders (typically the lowest-priority folders that get de-prioritised under cross-team sprint pressure). Velocity dropped, abandoned count rising. What changed? Standard playbook. (1) Open Tasks by Assignee (Workload View) and look for sudden concentration changes; a key person on PTO is the most common cause. (2) Open Wrike’s Workload View directly to see if any assignee is at capacity. (3) Cross-check whether sprint planning includes Vortex IQ findings; if findings are routinely deferred to “next cycle”, they accumulate. (4) Check whether a Wrike approval gate is bottlenecking; cross-functional teams often have approval-board delays that look like abandonment. The abandoned count appears suddenly higher overnight. Why? Because the 14-day clock keeps ticking. If five tasks were last touched on the same day exactly 14 days ago, all five become abandoned at the same time the next day. Normal and self-corrects within 24 hours of the team picking the queue back up. Should I close abandoned findings or fix them? Both, depending on triage. Run a weekly 30-minute “abandoned review” with one ops lead. For each: if no real merchant impact, mark Cancelled (Wrike’s terminal state for “won’t do”) with a comment explaining why. If real merchant impact, reassign and add to next sprint. We see Wrike merchants close 30 to 50% of abandoned findings on this triage as Cancelled; the remainder being correctly prioritised is the win. Can Wrike Automation auto-flag or auto-cancel abandoned findings? Yes (Business / Enterprise plans). Build an automation: Trigger: scheduled (daily 09:00) IF (custom_field:vortexiq_finding_id is set AND status IN [Active, Deferred] AND updatedDate < -14d AND priority NOT IN [High, Critical]) THEN comment "@assignee This finding has not moved in 14+ days. Triage today or mark Cancelled." AND apply tag "abandoned". Most Wrike merchants who adopt this see abandoned-bucket size drop 40 to 60% within a month. Why doesn’t Wrike ship an “abandoned” view natively? Wrike ships the filter primitives (Custom Field is set, Last Modified < X days ago, Status IN [...]) but not the curated view. The card’s added value: cross-folder aggregation, custom-status handling, threshold-based alerts, historical trend. Is this card the right primary watch metric for Wrike-using merchants? Yes. Findings Open tells you the queue size; this card tells you the queue health. On Wrike-using merchants the abandoned card is particularly important because Wrike’s strength (cross-functional request management) means findings can sit in approval-gate or cross-team-coordination limbo without anyone explicitly owning the next action. A finding important enough to fix manually but we never used Wrike to track it. Do we close the task? Yes. Set the task to Completed once the work is done. Otherwise it stays in the abandoned bucket. Vortex IQ does not auto-close findings just because the underlying audit signal cleared. My team uses Wrike for everything (marketing, creative, ops). Does the count include all teams? Yes if all relevant folders are tagged vortex_iq_outbound in connector setup. Wrike’s strength is cross-functional visibility; the card’s strength is the operational-discipline read across that visibility. If you want per-team breakdown, build a Stacked Panel with one panel per folder. Why is the alert threshold >5 / >15 and not higher? Wrike-using teams typically run smaller-volume audit programmes than Jira-using engineering teams. The thresholds are calibrated to that scale. Marketing-led merchants on Wrike with high finding volume should override warn up to >10 to reduce noise; engineering-led merchants on Wrike are rare but should override down to >3 for tighter signal. Wrike Work Intelligence accepted a suggestion on a task. Does that count as movement? Yes. Accepted suggestions update the task’s updatedDate, which the card watches. This is the correct behaviour because accepting an AI suggestion is an explicit human action even if a small one. Suggestions left unaccepted do NOT count.

​
Tracked live in Vortex IQ Nerve Centre

Abandoned Findings (>14d no movement) is one of hundreds of KPI pulses Vortex IQ tracks across Wrike (API) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.