Google Calendar sync duplicates meeting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tothewine
    Active Community Member
    • Jan 2018
    • 420

    #1

    Google Calendar sync duplicates meeting

    Hi,

    I have an issue with Google Calendar sync in EspoCRM.

    When I create an Meeting:
    • it is correctly created in Google Calendar
    • but a duplicate record is created in EspoCRM

    So:
    1 event → 2 records in EspoCRM

    Configuration:
    • Two-way sync
    • Scheduled job active
    • No workflows
    • Fresh Google reconnection

    Google shows only one event, duplicates are only in Espo.

    Is this a known issue or am I missing something in the configuration?

    Thanks
  • heint
    Member
    • Jun 2025
    • 81

    #2
    Greetings, tothewine,

    Since I'm unable to reproduce this issue on my side after some testing, please provide more details regarding it.
    - What Espo version are you using?
    - What steps do you follow to catch this issue? Is there any additional settings are you using to create meeting or extra custom fields?
    In any case, it's crucial to check the latest log file if you are using the self-hosted version, preferably with debug-mode enabled.

    Comment

    • tothewine
      Active Community Member
      • Jan 2018
      • 420

      #3
      thanks for your reply.

      Here are the details of my setup and how to reproduce the issue:

      Environment:
      • EspoCRM version: 9.3.4
      • Google Integration: 1.8.4
      • Outlook Calendar sync is enabled (two-way sync)

      Custom setup:
      • I created a custom entity called “Appuntamento”
      • It extends the Event template:
        class Appuntamento extends \Espo\Core\Templates\Entities\Event
      • No custom logic in:
        • Services (empty class)
        • Controllers
        • Hooks (none present)
      • No active workflows or BPM processes

      Steps to reproduce:
      1. Create a new record in the “Appuntamento” entity
      2. Save the record
      3. Immediately after saving:
        • One correct record is created (with all data)
        • A second record is automatically created, but empty (no meaningful fields populated)

      Important detail:
      The duplicate appears instantly after save, without any manual action.

      Additional checks already done:
      • Disabled all workflows → issue persists
      • Disabled Outlook sync temporarily → issue persists
      • Checked custom code → no duplication logic found
      • Checked DB table job → many jobs stuck in “Pending” (Google/Outlook sync included)

      Relevant log errors found:
      • Not a scheduled job
      • Espo\Modules\Google\Classes\App\JobRunner does not exist

      This makes me suspect there could be some issue with scheduled jobs or calendar integrations interfering, even if the entity is custom.

      Comment

      • heint
        Member
        • Jun 2025
        • 81

        #4
        As far as I know, using a custom entity that was created via the file system is not supported and might lead to several issues with some integrations like you've just described. Try to create a custom entity through the Entity Manager from the Administration Panel and check for any issues. Any updates would be appreciated here for further analyses.
        Last edited by heint; 04-14-2026, 02:55 PM.

        Comment

        • tothewine
          Active Community Member
          • Jan 2018
          • 420

          #5
          Hi,

          Thanks for your reply.

          Just to clarify: the entity was created via Entity Manager (not via filesystem), so it should be supported.

          The issue still occurs:
          • Google event is created correctly
          • Then a duplicate record is created in Espo
          • googleCalendarEventId is not populated
          • Logs show repeated 404 when trying to fetch the event

          So it seems the integration cannot properly map events for custom Event entities.

          Could you confirm if this is a limitation of the Google integration?

          Thanks.

          Comment

          • heint
            Member
            • Jun 2025
            • 81

            #6
            I did some tests and caught the duplicate/looping logic only if you have connected the same Google/Outlook external account on 2 different users in the same instance / 1 user (email address) in 2 different instances.
            Definitely it should not be the regular use case, and everyone should avoid this structure. In other cases, if you have a standard Google Calendar flow with no third-party extensions, that could impact any field of your custom entity (even in pairs with Outlook, which is not recommended); everything is working fine.
            There is no limitation on Google integration calendar sync; otherwise, users would detect and inform about this type of issue.

            Comment

            Working...