What's New · Stride

v1.3.0 — 2026-09-01

Tapping an activity's daily huddle button twice in quick succession now works at normal clicking speed. The second tap no longer gets dropped or snapped back a step — so reaching the red X takes two taps rather than three — and it no longer fails with an error. If a huddle can't be saved, the button returns to the last state that was actually recorded instead of showing one that was never saved, and clearing a huddle someone else already cleared now succeeds quietly rather than reporting an error.
New-baseline notification emails could silently fail to reach some team members on projects with many users, because sending them all at once exceeded our email provider's rate limits. Bulk notification emails are now paced to stay under the provider's limits (without delaying one-off emails like password resets), and any messages that are still rate-limited are retried once the provider's limit window resets.
Deactivated users no longer receive new-baseline notification emails.

Schedule exports no longer report 0 remaining duration for an in-progress activity whose planned finish has already passed — or falls on a non-working day right after the update window — when the days just past the window are non-working. Calendars that mark holidays, weather days, or event days as nonwork were most affected — the export now charges one working day, skipping ahead to the next real work day on the activity's calendar. Previously P6 read those activities as complete on re-import.

New View & Crew role: read-only schedule access plus daily crew (manpower) counts, for team members who report headcount but don't edit the schedule.
Crew counts are now tracked at the project level and are private to each subcontractor group, so they carry forward when a new schedule version is uploaded.
A public What's New page (this one) so you can follow Stride updates.

Dates entered from any browser time zone are now recorded correctly — some Windows time-zone configurations previously caused an error.
Fixed a validation that incorrectly blocked saving some actual start dates.
The crew and variance columns now line up correctly for roles that can't see Total Float.
Deleting a project now reliably removes all of its schedule data.

Hardening from our June penetration test, and expanded automated vulnerability scanning now covering the schedule-PDF processing service.