Time zone setting troubleshooting

If you experience issues with time zone settings, verify that the effective.timezone.basis setup is configured properly.

For example, the default time zone is EST. A candidate applies for a job on May 4 at 7 p.m. CST. The job application date is stored in Talent Acquisition as May 4 because the default time zone was set to EST.

• • If the effective.timezone.basis is set to system, then the effective date is set to the system date in UTC, which is May 5. If a recruiter tries to take the Hire action on the candidate on May 4, then an error message is shown stating the candidate does not exist.
  • If the effective.timezone.basis is set to corporate, then the effective date is set to the default time zone date, which is May 4. If a recruiter tries to take the Hire action on the candidate on May 4, then no error is generated, and the hire runs successfully.
• When you specified an effective date, such as for the Hire action, was it based on your time zone settings?

  For example, the default time zone is EST. The candidate applies for a job in on May 4, at 11 p.m. CST. The job application date is stored in the system as the following day: May 5, due to the default time zone setting of EST. A recruiter in Pacific Standard Time (PST) tries to hire the candidate on May 4 at 11 p.m. PST. If the recruiter chooses an effective date on the hire action of today, May 4, then the recruiter receives an error message on the hire action, because candidates cannot be hired before they have actually applied.