Skip to main content

Troubleshooting Date/Time Field Update Issues in Workflows (CRM)

If workflows are returning incorrect dates (like 12/31/1969 7:00 PM) when updating Date/Time fields, or if Date/Time field configuration options aren't loading in workflows

Before You Begin

  • Verify that you're experiencing one of these specific symptoms: Date/Time workflow fields returning epoch date (12/31/1969) or Date/Time field options not loading in workflow configuration

  • Have your workflow name and affected Date/Time field names ready

  • Note which module (Intake Opportunities, etc.) is affected

Steps to Resolve

  1. Document the Issue: Take a screenshot or Loom recording showing the Date/Time field behavior in your workflow

  2. Contact Support: Submit a support ticket describing the specific Date/Time field issue you're experiencing

  3. Provide Details: Include your instance URL, workflow name, affected field names, and any evidence you captured

  4. Wait for Escalation: Our support team will escalate this as a global bug to our development team

  5. Test After Resolution: Once notified that the fix is complete, test your workflows to confirm Date/Time fields are updating correctly

Expected Result

After the issue is resolved:

  • Date/Time fields in workflows will show current date and time instead of 12/31/1969

  • Date/Time field configuration options will load properly in workflow setup

  • Stage change timestamps and other Date/Time automations will work as expected

Temporary Workaround

While waiting for the fix, consider creating a single "Master" timestamp field that updates whenever any relevant stage changes occur. This provides visibility into recent account activity without requiring multiple Date/Time field updates.
​

Common Symptoms

  • Epoch Date Display: Workflows showing 12/31/1969 7:00 PM instead of current date

  • Configuration Options Missing: Date/Time field options not loading in workflow "Update Field" actions

  • "Get time Today" Function Failing: Existing automations returning incorrect timestamp values

Related Resources

Did this answer your question?