Calendar View potential bug

Hi, I tried to find related topic but couldn’t so decided to create new one.

Take a look at the calendar view in my app (especially the red annotation):

There is no event that should be visible but when I try to search or filter by specific criteria it starts showing up. Is there any specific reason why the calendar would behave like that?

I never heard about any limits in such views/cases. Maybe someone could help me understand what am I doing wrong?

Here is how this view is configured

Thanks in advance! :folded_hands:t3:

Hi mateo,

I rebuilt this in a test app and got the same thing. The most likely cause is one event whose End is before its Start (or is blank). The day view draws that event as a huge block to the end of the day and covers anything underneath it. Searching filters the bad event out, so the hidden one appears.

Fix: check the End times of the events before the missing one that day, correct the bad one and sync. To stop it happening again, add a Valid_If on End: [End] >= [Start].

(Overlapping events weren’t the problem in my test. Eight in the same two hours all still showed.)

Hi @jarrod_eskimojoe

Thanks a lot for taking the time to rebuild this in a test app and trying to help! I really appreciate it. I double-checked my database based on your suggestion, but it looks like all the Start and End times are actually perfectly valid. None of the events have a blank end time, and every end time is correctly set after the start time. We use validations for blanks and [End] >= [Start].

Here is the anonymized and stripped-down data directly from my database for that specific morning:

The event that gets hidden:

  • ID: [hidden-event] | Start: 2026-10-27 09:00:00 | End: 2026-10-27 10:00:00

The previous/overlapping events (which are visible):

  • ID: [event-1] | Start: 2026-10-27 07:30:00 | End: 2026-10-27 08:30:00
  • ID: [event-2] | Start: 2026-10-27 08:00:00 | End: 2026-10-27 09:00:00
  • ID: [event-3] | Start: 2026-10-27 08:30:00 | End: 2026-10-27 09:30:00
  • ID: [event-4] | Start: 2026-10-27 08:30:00 | End: 2026-10-27 09:30:00

As you can see, the time entries are solid. My current theory is that this is actually a UI limitation in AppSheet’s calendar view. Because there is a high density of overlapping events (up to 4-5 events between 8:00 AM and 9:30 AM), the engine might run out of horizontal space to draw the 5th tile side-by-side, effectively dropping it from the view (?).

Did your test app have this exact level of overlapping density in a single time slot? It really looks like a hard limit on how many concurrent columns the calendar can render. Interesting is the fact that it also breaks on desktop, not only mobile.

Thanks again for looking into this! :heart_eyes:

Hi mateo,

You are right, and I owe you a correction. I rebuilt your exact five rows in a clean test app, all valid, no blank ends, every End after its Start, and the 09:00 to 10:00 event vanishes from the Day view just like yours. Searching for it brings it straight back, full width at 9am, so the row is fine and correctly placed. It is a rendering problem in the calendar, not your data. My earlier answer about checking the End times does not apply here, sorry for sending you that way.

I also tested the out-of-space theory, and it does not hold up. Three events overlapping the same slot (a 9:00, 9:15, 9:30 staircase) all draw fine in three columns. Two identical events plus a third also all draw. And adding a sixth event to your set does not hide any more, it is still just the one tile missing. So it is not that the day is too full.

What breaks it is the specific arrangement. With your five rows the 09:00 event gets zero width and disappears, and taking one of the overlapping events back out brings it back. It looks like the layout engine miscounts columns for certain overlap chains (yours runs 7:30 right through to 10:00) and collapses one tile to nothing. Telling detail in mine: the 7:30 to 8:30 event draws full width even though the 8:00 event overlaps it, which is the first sign the column maths is off.

Two things from here:

  1. This is worth reporting to Google as a calendar rendering bug, since the data is valid and it reproduces cleanly.

  2. In the meantime, because the data is intact, the safe workaround is a second non-calendar view of the same table, a deck or table grouped by start time, so a dense day never hides anything. Keep the calendar for the overview, let the list guarantee nothing goes missing.

Happy to compare notes if you test other patterns.

Jarrod

Thanks again Jarrod!

I am glad you confirm my observations as I already spent quite some time trying to understand where I could make mistake. Your suggestion with separate view to include every row is already live in the app. That way the client actually let me know about the missing event.

I am wondering now whether I should create a support ticket or this thread is enough. I noticed over years that this community has more power than chat with support. Let me tag you @Jose_Arteaga, as this seems quite a bug. Mamy companies use calendars for their everyday operations. Missing events can cause real problems.

I hope this discussion will help AppSheet team find the actual cause and fix it OR (!) give me instructions on what is wrong on my and Jarrod’s side.

Hello @mateo,

I was unable to replicate the issue (see below). The best option at this point would be to reach out to the support team and enable access to your application so that they can review directly.

Let me know the ticket number so I can directly follow up

Thanks for trying to rebuild this yourself Jose! Truth is that your trials don’t cover the complexity from my case and that’s probably why you weren’t able to to reproduce that behavior. I will contact support though and share ticket ID here.

Ticket ID: 77019110 (Workspace official support)

Is there any update on this by any chance? :folded_hands:t3:

Did Support do anything?

I got info they do something, that’s all

I just checked and the engineering team is still working on it

Hello all,

Thank you for your patience while our engineering team investigated this issue.

Update & Findings:
The engineering team has successfully reproduced the behavior internally using the event data shared. They have confirmed the underlying data is completely intact and correct.

Root Cause:
This is a known display rendering bug specifically affecting the Calendar Day and Week views. When certain events overlap in time, one event is inadvertently drawn directly on top of another, hiding it from view. When you use the search function, it filters out the overlapping conflict, which is why the hidden event suddenly reappears.

Workaround:
Until our team rolls out a permanent fix, you can temporarily use a Deck view or Table view of the same data source, which will display all overlapping events without hiding them.

The engineering team is actively working on a fix for this and they will provide an update as soon as the fix is ready for testing.