CRITICALFailure Reference

Runway Watermark Bleed-Through — Refund Guide

Technical Classification

Watermark Pipeline Misrouting

Watermark Pipeline Misrouting occurs when Runway's post-generation watermarking module fails to recognise the user as a paid-tier subscriber and applies the free-tier watermark anyway. This is the single strongest refund-grounds defect because it directly contradicts the paid-tier deliverable. Affects users immediately after plan upgrades, billing renewals, or session boundary crossings.

How to identify this failure

✕Visible Runway watermark in corner of paid-plan output
✕Watermark appears even though billing dashboard shows active paid plan
✕First few generations after plan upgrade still watermarked
✕Some generations watermarked, others not, in the same session
✕Watermark removal tool reveals trace residue in pixels

Real generation examples

Prompt used

Any prompt on a Standard or Pro tier account immediately after upgrade

Failure observed

Output delivered with bottom-right Runway watermark visible despite paid tier

Prompt used

Bulk generation session — 5 of 12 outputs watermarked

Failure observed

Inconsistent watermarking within single session despite continuous paid status

Documentation strength

If you need to escalate

VERY HIGH — strongest refund grounds in the Runway product. Billing-feature defect, no creative-variance defense available.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Watermark Pipeline Misrouting pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Watermark Pipeline Misrouting first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Watermark Pipeline Misrouting". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Will Runway support escalate watermark-bleed failures?

Yes — this is the strongest refund grounds in the product. Billing-feature defects are not subject to creative-variance defenses. Refunds are routinely instant.

Why does the free watermark appear on paid output?

The watermarking module reads user-tier state from a cached entitlements lookup. On session boundaries or plan upgrades, this cache may serve stale free-tier state.

When is watermark-bleed risk highest?

Immediately after plan upgrade, immediately after billing renewal, on first generation of a new session, or after a long idle period. AVA checks tier metadata against rendered output automatically.

Catch it before you generate

AVA scores this failure mode against your prompt in real time

Free Chrome extension. Analyzes your prompt as you type, flags failure-prone patterns specific to this model, and tells you what to rewrite — before you commit credits to a generation that will fail.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders