Are you guys still not seeing your work history updating?? Yarbo replied to my ticket yesterday saying that they were working on it. I’m curious to know if this is a global problem, or just a sporatic hit or miss type of thing.
If it’s a global issue, this is another case where they should be putting out a “Known Issues” communication to everyone.
They replied to a FB post this morning they are aware and looking into it. Agreed, known issues should be communicated and should pop up when trying to open tickets for them.
I just got another reply to my ticket…
“This issue was previously identified as a bug and has already been resolved by our R&D team. We have not received any similar reports recently, so it appears to be specific to your unit.
We are currently consulting with the relevant team, and we will update you as soon as we receive further information.”
Let them know it’s not just you. Lol
Yeah, I updated the ticket suggesting that they check this thread because multiple people are reporting the same issue.
Same. I opened a ticket as well. @rgloverii
I guess your Yarbo took a weeks vacation! 
Good news - Yarbo has fixed my Work Plan history.
They said they ‘remotely fixed the issue’, which suggests it was a problem on my Yarbo itself, versus a database problem on the back end.
Now the question is - Is anyone else still having issues with their history?
Miraculously mine is working again.
At least missing jobs have shown up.
Mine showed up now too. Sounds like a backend problem. Glad it’s fixed!
Back end problem…. I thought it was all on the core. Silly me…
My guess would be app to core. I’m sure it’s probably still stored on the core.
Glad to hear it’s resolved for everyone!!
And interesting that the ‘fixed it remotely’ seems to have fixed it for all.
I had a ticket for this too and I can confirmed my was fixed this morning as well along with the confirming email it was fixed.
mine is suddenly back too. Must have been a busy night updating everyone’s cores….especially since mine was shutdown… /s
That confirms it was a backend issue.
Yup. At least wer’re all back online again. But funny how the explaination I was given wasn’t entirely accurate.
