Calendar yearly Recurrence date is shifting to 1 year later than expected

Aspose.Email Product Family
1

Environment Details
• Aspose.Email Version: 25.8.0
• .NET Version: .NET 8
• Integration: Microsoft Graph API via IAsposeGraphClientProvider

Expected Behavior: Meeting created for October 11, 2025, should recur yearly on October 11.
Actual Behavior: Meeting is created in the next year with the current month (September 11, 2026) instead of the specified date.
Test Case:
{
“startDateTime”: “2025-10-11T01:00:00Z”,
“endDateTime”: “2025-10-11T03:00:00Z”,
“recurrence”: {
“frequency”: “Yearly”,
“interval”: 1
}
}

Result: Creates meeting on September 11, 2026, instead of October 11, 2025.

2

@LNGLEEVFDEV

It appears that the issue with the calendar yearly recurrence date shifting to a year later than expected may be related to how the recurrence is being set up in your code.

In your test case, you are specifying the start date as “2025-10-11T01:00:00Z” and setting the recurrence frequency to “Yearly” with an interval of 1. However, the actual behavior shows that the meeting is being created on “September 11, 2026” instead of the expected “October 11, 2025”.

Here are a few things to check:

  1. Time Zone Handling: Ensure that the time zone is correctly set when creating the meeting. If the time zone is not specified, it may default to UTC or the server’s local time, which could lead to unexpected shifts in the date.

  2. Recurrence Rule: Verify that the recurrence rule is being applied correctly. You might want to explicitly define the recurrence pattern to ensure it adheres to the expected date.

  3. API Limitations: Review the documentation for the Aspose.Email API and Microsoft Graph API to ensure there are no known issues or limitations regarding yearly recurrence settings.

If the problem persists, consider providing a minimal reproducible example or checking community forums for similar issues.

3

Doubtful that it’s Timezone related as stated : Creates meeting on September 11, 2026, instead of October 11, 2025.

Here is a sample as requested:
CreateYearlyRecuranceMeeting.zip (978 Bytes)

4

Hi @LNGLEEVFDEV
Thanks for the additional info. We were able to reproduce the issue with the skip October 11, 2025, but were unable to reproduce the issue with the September event creation. Could you provide the resulting ics file after saving?

5

@LNGLEEVFDEV
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): EMAILNET-41640

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

6

Actually we do have paid support, but i logged this in general support I guess. Can this ticket be linked to paid support or will it need re-raising?

7

@LNGLEEVFDEV,

This issue has already been fixed, and the fix is available in the published 25.9 release.