Or running a script purging on page load.

u apparently should not to do this. cuz it seems like tou violation: You will not: (i) take any action that imposes, or may impose in our sole discretion an unreasonable or disproportionately large load on our infrastructure;

i'd rather suggest to contact to staff. in order to improve poll behavior to update numbers.

They have to. Otherwise they admit to let it stay a buggy feature not recommend to use.

Is this your pull request? Because each pull request should usually have a JIRA ticket number which is obtained by contacting Staff through Special:Contact/general. Did you contact Staff before making that pull request?

And yes, AjaxPoll is a buggy feature not really recommended for use. There are other poll integrations you can use, from what I've heard, though.

What really needs to happen is Fandom needs to find or make a better poll extension. None of the ones they have are any good.

Unfortunately to be honest, the german staff is not literally open-minded when it comes to feature requests, improvement proposals and things like tat...

Which other polls integrations are available as extensions and recommended to use in favor of AjaxPoll?

Okay, so we are in agreement about AjaxPoll causes this misbehavoir, there are just workarounds we have to aquire a taste for and Fandom staff is responsible to change that.

Are you look for w:c:dev:MassNullEdit by chance? It's helpful to purge all pages that use a template you recently updated.

That is done manually, right?

Unfortunately, engineers don't merge pull requests that aren't made by Staff and don't have a valid JIRA ticket associated.

Looks like PollSnack and Polldaddy tags are available.

<pollsnack hash="qhc56i3c" />
<polldaddy id="9801404" />

gives... (click the link to the right to expand)

So one of my pull requests seems to be merged by accident... Anyways: If the staff member has opened a JIRA ticket at any time, she did never tell me...

Thanks. I will try them out (Y)