Retro elements not calculating after old element deferred in event notification
Summary:
Any employee with an element deferred in the past (element is never paid out) is impacting the ability for new (current pay) retros to not process. Should these events be cleaned up? Is there a best practice to allow employees to have (current) retros process without being impacted by old/historical ones?
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
25D
Code Snippet (add any code snippets that support your topic, if applicable):
Tagged:
1