Email To case emails are always in "Being Imported" Status

[abhilash.kumar.niit]

Hi i am using email to case for my espocrm. Sometimes the inbound emails are not mapped with the case and their status is also "Being Imported" instead of Archive . Any solution or suggestion?? what i am doing wrong please help.

[Vadym]

Hi abhilash.kumar.niit,

Are you using external email client for emails fetching?
Please provide EspoCRM error log and screenshot of Group Email Account to get more details about your issue.

[abhilash.kumar.niit]

Hi Vadym,

Yes, i am using external email client for fetching the emails to the espo system. ESPO error log has a single error "[2024-09-05 05:01:46] ERROR: WebSocketSubmission: Class "ZMQContext" not found"

[esforim]

I'm noticing ever since 8.4 everything seem to be Imported whenever it fetched email.

[yuri]

We just changed the label in 8.4. Archived => Imported.

[esforim]

Thank you for that clarification. Personally it don't affect anything but "eye muscle memory" seeing the difference but don't remember what was it previously.

[abhilash.kumar.niit]

Hi espocrm i have the 8.3 version of espo it works fine but some time the emails are not being imported correctly the status shows " Being Imported" for always.

[yuri]

Would "o-data" username be fine?

[esforim]

If there no other choice, please change it to: esforim yuri

With my 4 years here, I think only 2 people PM me thinking so, but I quickly shot them down to post it a thread.

An early RIP to espcrm and hail the @esforim

[yuri]

Done. Renamed to esforim. I hope your previous password should still work.

[yuri]

Try disabling websocket. Administration > Settings > Uncheck "Use WebSocket" and save.

[abhilash.kumar.niit]

Hi Yuri , 

Thanks for the reply i have disabled the web socket but yet getting the same issue my emails are not being imported in the system. Can you please help me what wrong i am doing??

[yuri]

What else in the log since you disabled websocket?

[abhilash.kumar.niit]

Hi yuri,

unfortunately it happens occasionally and below is the given error from logs.

Accessing related records with Entity::get is deprecated. Use $repository->getRelation(...)->find()

[partomas]

We encountered the same issue with emails having the 'Being Imported' status. It seems that not all emails are fully imported—some are 'partially' imported and remain stuck with this status.

A potential solution from ESPOCRM side could be to mark these emails as not imported and attempt to import them again during the next interaction.

Currently, it appears that these emails are skipped in subsequent import attempts, and there is no way to manually trigger their import.

[abhilash.kumar.niit]

Yes, i too think there should be a way to trigger import again, also i have observed that it happens when the "Check Group Email" job is failed...

[partomas]

Yes, exactly, today I looked more retailed in the samples and i can confirm that "that it happens when the "Check Group Email" job is failed" Might be yuri could find a solution fow to resync such mails as they have clear indication of failure?

[abhilash.kumar.niit]

Yes,i wish there could be button of reattempt sync on failed jobs page

[Laimonas]

abhilash.kumar.niit Have you found a way to fix the Email status "Being Imported" issue? We are experiencing the same problem. As a temporary workaround, I created a workflow that changes the status of these emails to "Imported" so they are visible to CRM users. However, some issues persist when the Group Email Account fails to import an email:

1. Attachments are missing from these emails.
2. The "from" and "to" fields are not populated.
3. New emails do not create a Case as expected.
4. Error log says: "ERROR: InboundEmail 5db6d578947bfa472, import message; 1205 Lock wait timeout exceeded; try restarting transaction"

We tried increasing the innodb_lock_wait_timeout parameter from 50 to 100, but unfortunately, it didn’t solve the issue.

Any insights or solutions would be greatly appreciated!