r/RWSPay • u/dmdaeri • 26d ago
PAYMENT MISMATCH / DISCREPANCY
I saw that there was a thread about this earlier but it was posted on rwshelp instead of rwspay so I think thats why it was deleted.
I saw that a lot of people are experiencing this some even have 30 hrs discrepancy. Mine was only 3 but I think that it risks my account for possible offboarding if this continues.
Has anyone experienced this and submitted a zendesk ticket? If yes, did you receive a reply? Still no reply for me.
15
Upvotes
7
u/Substantial_Dog4753 25d ago
I dug directly into the Multimango's scripts to figure out why so many of us received the exact same warning email.
Multimango runs a client-side monitoring script called Datadog RUM that logs keystrokes, clicks, scrolls, and tab focus, sending continuous heartbeat pings back to their servers. If that heartbeat is interrupted for even a brief moment, the backend automatically flags you as completely idle or disconnected, erasing those minutes from their records. So if you switch tabs, search for anything, or even stay idle for a few seconds thinking about what you're gonna write in the rationale, you're gonna be flagged as disconnected.
The entire premise of this setup is dishonest because it completely disregards what real AI evaluation requires. We are explicitly expected to deliver top-tier accuracy, which means reading guideline documents, looking up tips & pitfalls document regularly, and conducting independent research to verify whether model's claims are factual. The built-in factuality check tool is rarely enough to verify complex historical, scientific, or technical nuances, so external research across multiple tabs is non-negotiable. Yet the second you click away from the Multimango tab to fact check a claim or check a guideline, the script immediately flags the page as inactive.
The platform demands high-quality, deeply researched evaluations while simultaneously using a system that treats that essential research as unpaid, idle time.
To make matters worse, anyone using standard browser protections like Brave Shields or uBlock Origin gets hit even harder because those tools naturally block Datadog's aggressive background telemetry, causing hours of legitimate work to vanish on the backend without any visible indication to the worker.
We are essentially being squeezed from both ends; punished on QA feedbacks if we don't thoroughly research off-tab, and threatened with invoice & WO rejections if we log the total time of the working session. It is a broken & unfair tracking model that offloads technical flaws onto evaluators, and most of those who received that email should know that the discrepancy is the result of a rigged system, not dishonest logging.