Automation Monitoring App Down :(

Actually it does for me. Last day didn’t show logs that 30 days did

@Jose_Arteaga , what update?

Thank you so much @Steve.
I sincerely apologize that I cannot provide a definitive update at this moment. Please be assured that I have escalated the case, and our engineering team is actively working towards a resolution. I am monitoring the progress closely and will reach out to you as soon as more information becomes available.

Hi @SkrOYC

Thanks for sharing …

@Steve Latest update last night.

Hello @Denzil_Snyman, we have an update from the engineering team - We identified the problem is a combination of a limit on how many total recent rows are returned, and a different automation producing a large number of logs (due to running for-each-row) that end up filling up most of that row limit. We haven’t identified an easy fix for this - simply increasing the row limit is unlikely to make a big difference for the lower volume automation of interest (doubling the limit might mean you only get 10 logs instead of 5). We are considering more granular filtering as a potential workaround.
I truly appreciate your patience and will be sure to keep you updated as I receive more information.

@Shourya_Tomar, what progress?

Hello @Steve, I am sorry I do not have any more updates to share at this point in time. I will follow up with the team and keep you updated.

@Shourya_Tomar, any news to share?

Hello @Steve, I am sorry I do not have any updates to share at this point in time. I will follow up with the team and keep you updated.

Still waiting, @Shourya_Tomar

Any update, @Shourya_Tomar ?

I’m guessing @Shourya_Tomar no longer exists. @Jose_Arteaga?

Anyone working in appsheet dev team anymore ? we barely see any updates.

Hello all,

I just pinged the support team asking for updates on this. I will let you know as soon as I hear back from them.

Any update, @Jose_Arteaga?

Thanks for the follow up @Steve,

A fix deployed on August 28th produced inconsistent results. The case was reassigned to the engineering team yesterday for deeper investigation.

We do not have further updates just yet, but the team is actively looking into the discrepancy.