Forum Analytics Error

[bigballofyarn]

Analytics URL: bigballofyarn.proboards.com/admin/marketing/analytics

I think this is the first time I've ever seen a blue bear on the analytics page. I'm just making a report in case there ends up being a bigger issue.

[Scott]

bigballofyarn, thanks for bringing this to our attention. I've alerted systems.

[dustys]

It's down still?

[Michael]

Hi,

This is still being worked on. Apologies for the issue!

[Webster]

I was wondering what was wrong w/the Analytics page; now I know.

[Michael]

Hi,

This should now be fixed!

[bigballofyarn]

Aug 20, 2019 16:25:04 GMT -8 Michael said:

Hi,

This should now be fixed!

I presume it wasn't able to keep proper records during the outage, correct?  The numbers I am seeing for the 20th are incorrect. However, I can access the analytics once again and it looks like everything is working, with the exception of the Tapatalk issue we discussed in another thread.  Thank you to you and the rest of the Proboards team for resolving this. You guys are great.

[Michael]

Aug 20, 2019 17:06:49 GMT -8 bigballofyarn said:

Aug 20, 2019 16:25:04 GMT -8 Michael said:

Hi,

This should now be fixed!

I presume it wasn't able to keep proper records during the outage, correct?  The numbers I am seeing for the 20th are incorrect. However, I can access the analytics once again and it looks like everything is working, with the exception of the Tapatalk issue we discussed in another thread.  Thank you to you and the rest of the Proboards team for resolving this. You guys are great.

They may not be correct now but they should update to more accurate numbers as everything catches up. I'm pretty sure (because of ad-free) they should fix themselves. 

[dustys]

Does it make counts with the apple proboards app?

[Scott]

Aug 21, 2019 6:41:16 GMT -8 dustys said:

Does it make counts with the apple proboards app?

The ProBoards app was discontinued years ago and it was ultimately replaced by compatibility with Tapatalk.

[bigballofyarn]

I'm guessing things are down again. I'm just updating my original post.

[dustys]

Yeah errors all around my mom's forum too

[Lynx]

Nov 17, 2019 5:55:26 GMT -8 bigballofyarn said:

I'm guessing things are down again. I'm just updating my original post.

Just to note - the last post was made in August. I believe (subject to correction) that, if a thread has not been replied to in 30 or more days, a new thread should be started. This is because this thread may have been internally marked as resolved in the interim. You are always free to link back to this thread.

Nov 17, 2019 6:02:03 GMT -8 dustys said:

Yeah errors all around my mom's forum too

Although you had hijacked this thread earlier, you should create your own thread. While the issue may appear to be the same, the resolution may not be. By having your own thread, the proper personal attention can be given to your issue.

[dustys]

Nov 17, 2019 6:36:55 GMT -8 Lynx said:

Nov 17, 2019 5:55:26 GMT -8 bigballofyarn said:

I'm guessing things are down again. I'm just updating my original post.

Just to note - the last post was made in August. I believe (subject to correction) that, if a thread has not been replied to in 30 or more days, a new thread should be started. This is because this thread may have been internally marked as resolved in the interim. You are always free to link back to this thread.

Nov 17, 2019 6:02:03 GMT -8 dustys said:

Yeah errors all around my mom's forum too

Although you had hijacked this thread earlier, you should create your own thread. While the issue may appear to be the same, the resolution may not be. By having your own thread, the proper personal attention can be given to your issue.

the last post was this morning. I hijacked her post again earlier. She replied again. I deleted my post. Then I replied again. So it's my fault. Seemed to make more sense to keep one error all together Sorry. Anyway we can wait for the admins to address the analytics error.

[Scott]

bigballofyarn and dustys, basically confirming what Lynx posted above.

If the issue is resolved and happens again a couple weeks later, please start a new thread. We internally marked this thread as resolved and had associated with the issue in August.

Thanks.


And by the way, the issue for today has been fixed.