This has been resolved. When attempting to update or submit an activity with a custom date field of nil, an error page was displayed. This issue was just introduced with a fix to a custom date field display issue. The original fix validated the format of the custom field date value so that it could be parsed correctly. This fix, however, did not account for an empty or nil date. When a nil was encountered, checks failed resulting in the reported error.
Note: The custom date field validation change will be included in an upcoming release.
Posted Oct 02, 2025 - 16:00 EDT
Monitoring
A fix is in the process of being implemented.
Posted Oct 02, 2025 - 14:23 EDT
Identified
The cause has been identified, and our team is actively addressing it. We’ll provide more updates as we move toward resolution.
Posted Oct 02, 2025 - 12:58 EDT
Investigating
Earlier today users began reporting an issue in the application when updating activities. This is currently under investigation with updates to follow.