FAQ

Where do I start?

Start with the Getting Started page for a quick overview, then move into Guides for step-by-step workflows.

How do I report a problem?

If the answer is not in the docs, contact your team lead or submit feedback through the app when available.

Who updates these docs?

The support team maintains this site and adds new guides as features evolve.

Why does saving an event show “Invalid date or time” during clock changes?

During Daylight Saving Time transitions, certain times on the clock are ambiguous or do not exist in your organization’s local time zone:

• Autumn clock change (repeated hour): When clocks fall back (for example, between 1:00 AM and 1:59 AM in US time zones), that hour happens twice. The platform does not guess which occurrence you mean, so entering a start or end time in that repeated window is rejected with “Invalid date or time”. Schedule the event before 1:00 AM or at 2:00 AM and later.
• Spring clock change (skipped hour): When clocks jump forward (for example, from 2:00 AM to 2:59 AM in US time zones), times within that hour do not exist on the local clock, resulting in the same error. Schedule the event before 2:00 AM or at 3:00 AM and later.

If an existing event was already stored inside that hour, it cannot be re-saved until its start and end times are updated outside that window. When editing an existing overnight event that crosses a clock change, the platform derives the next-day end date and elapsed duration automatically, unless the start or end time falls inside the repeated or skipped hour.

For more details, see Daylight Saving Time and clock changes.