Guildacitivies shows a big tick despite NOT having 600 tickets

[Winddancer2301]

Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Asus ZenPad
OS Version 7.0
Ally Code: (Find it here: http://bit.ly/AllyCode ) 473-657-433
What type of issue do you have? Gameplay
How often does the bug occur? Occasionally (10% - 49%)
Summarize your bug Even though the guild activies tab shows a big tick for finished personal raid tickets, the counter is NOT 600.
Steps: How can we find the bug ourselves? Sorry, no idea. was reported to me as guild leader by a guild member that got told off for missing his daily 600.
Connection Type
Please select your region
Country

‌

This is the screenshot my guild mate, Areal Striph posted me on our discord channel. I entered his Ally Code in the above selection, so you can check with the correct account.
He also told me he spent an additional 30 energy, but the counter remained at 504.

[EA_HighCommand]

Hi @Winddancer2301 and thank you for the report.

Did this only happen on Saturdays/Sundays, when the daily Guild activity is PvP battles?

As for the 30 additional energy spent, did he also check the guild section (which is usually updated faster and therefore more accurate)?

[Winddancer2301]

We both checked it guild section. I even closed the game and restarted it, no change.

As for only happening with certain activites, sorry, no idea. We just noticed yesterday and I did the report immideately. Will have an eye on it now though.

[EA_HighCommand]

Thank you for the swift update @Winddancer2301, much appreciated.

Please keep in mind that it can take up to 5 minutes before the Raid Ticket statistic is being updated (usually it's much faster within the Guild section).

We will keep an eye on it throughout the week, but as of today, we couldn't find any issue.

If you see it again, please update the thread. Thank you!

[badsmack]

I’ve logged 600+ tickets but in game shows 552. 

In game name

DarthJarJar DŁ

[Grandepatron]

Let's bring this back up. Not sure this is completely fixed.