@neilarey - I had noticed months ago that there is an issue with how cookies are being managed by browsers using DAREBEE. If too many triggers are activated in any programs or challenges, the cookies were storing too much data for what the server's header field is set for and then a 400 error would eventually come up for all pages that had tracking cookies associated with them. Clearing all cookies was the only way to resolve the issue.

Hence why I started to keep track of everything on a spread sheet just in case I had to clear my cookies again.
Having been a beta tester for MAC & Windows O/S, various games, and community servers, I naturally had to test a theory out with all of the browsers installed on my computer (Chrome, Brave, Opera, Firefox, Edge, UR Browser, TOR) and the issue was prevalent in all of them. Chrome held out the longest and was able to handle 10 challenges having all days marked as complete (aka 300 triggers) before the 400 error came up. My main browser, Opera, could only handle 3 (aka 30 triggers) before bringing up the 400 error. The rest of the browsers were all over the place in between those two.
Now, if I only tracked the day I finished and cleared the previous one(s), say clicking day 18 as complete but clearing day 17 and any days before that, then my browsers didn't go over the header limit and everything stayed fine with my current P&Cs. I did also discover that regardless of browser, even having just the final day marked in a P&C along with any workouts marked as done brought up a 400 error if I had 64 or more pages being tracked.
After testing my theory, I started to move all finished P&C's to a 'done' list I had created in the Bookmarks section and unclicked any tracking indicators that were on them. That way, I was keeping my tracking cookies down to a manageable level and wouldn't have issues with my latest crop of P&Cs, but still had a way to track which ones were done. Win/win!
I just went into the new dashboard and it looks lovely but did see that none of my completed P&Cs were listed. Because I didn't have every day marked as finished, just the final day, it was not considered 'done' by the servers. Maybe something the developers could think about.

After checking each day though, yes, 'DONE' was then triggered on all three pages, BUT after the 3rd page was registered as done, the website, once again, brought up the 400 error like it had in the past. Back to clearing my cookies (dammit) and going into all of my current P&Cs to once again mark the last day I completed. Oi.
Hopefully what I have noticed, and what I have been doing to deal with the problem, will help your developers out in any tiny way.
