# API polling missed deactivations and could return the wrong tradeflows

**URL:** <https://community.dockflow.com/t/api-polling-missed-deactivations-and-could-return-the-wrong-tradeflows/76>\
**Category:** Known and fixed issues\
**Created:** [November 6, 2026, 2:41pm UTC](https://community.dockflow.com/t/api-polling-missed-deactivations-and-could-return-the-wrong-tradeflows/76 "2026-11-06T14:41:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [November 6, 2026, 2:41pm UTC](https://community.dockflow.com/t/api-polling-missed-deactivations-and-could-return-the-wrong-tradeflows/76/1 "2026-11-06T14:41:50Z")

</div>

**Status:** Fixed since April 2026

**How to recognise it**  
While the problem existed, your polling did not receive deactivations. A tradeflow you set to inactive stayed active in your system. Polling could return tradeflows older than the requested time. That could corrupt your polling cursor. Active-only requests could still include inactive tradeflows. Inactive tradeflows could reach your ERP.

**Which shipments this affects**  
Tradeflows whose active state changed. Polling requests that used a since time. Requests that asked for active tradeflows only.

**What changed**  
Deactivations now reach your system through polling. Polling no longer returns tradeflows older than the requested time. Active-only requests now return only active tradeflows.

**Is past data corrected?**  
No. The fix applies from that month on; earlier data stays as it was.

**How to check your shipment**  
In your system, open a tradeflow you set to inactive and confirm it now shows as inactive. Also check that an active-only view shows no inactive tradeflows. If either check fails, contact support.

**Do you need to do anything?**  
Nothing.