Hi,
Support team from my hosting found this error that is causing the issue:
[13-Apr-2021 07:02:34 UTC] WordPress database error Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '=' for query SELECT *, EHT.id as email_history_id, ETT.id as email_template_id FROM wp_cartflows_ca_email_history as EHT
INNER JOIN wp_cartflows_ca_cart_abandonment as CAT ON EHT.<code>ca_session_id</code> = CAT.<code>session_id</code>
INNER JOIN wp_cartflows_ca_email_templates as ETT ON ETT.<code>id</code> = EHT.<code>template_id</code>
WHERE CAT.<code>order_status</code> = 'abandoned' AND CAT.unsubscribed = 0 AND EHT.<code>email_sent</code> = 0 AND EHT.<code>scheduled_time</code> <= '2021-04-13 09:02:34' made by do_action_ref_array('cartflows_ca_update_order_status_action'), WP_Hook->do_action, WP_Hook->apply_filters, Cartflows_Ca_Cart_Abandonment->update_order_status, Cartflows_Ca_Cart_Abandonment->send_emails_to_callback
[13-Apr-2021 07:02:34 UTC] WordPress database error Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,IMPLICIT) for operation '=' for query UPDATE wp_cartflows_ca_cart_abandonment as ca SET order_status = 'lost' WHERE ca.order_status = 'abandoned' AND DATE(ca.time) <= DATE_SUB( '2021-04-13 09:02:34' , INTERVAL 30 DAY)
AND ( (SELECT count(*) FROM wp_cartflows_ca_email_history WHERE ca_session_id = ca.session_id ) =
(SELECT count(*) FROM wp_cartflows_ca_email_history WHERE ca_session_id = ca.session_id AND email_sent = 1) ) made by do_action_ref_array('cartflows_ca_update_order_status_action'), WP_Hook->do_action, WP_Hook->apply_filters, Cartflows_Ca_Cart_Abandonment->update_order_status
Notably, this indicates that utf8mb4_unicode_ci,IMPLICIT and utf8mb4_unicode_520_ci,IMPLICIT cannot be collated because there is an equal coercibility between the strings, preventing MySQL from favoring one for collation. This error is typically indicative of two tables using equally valid but incompatible collation. One solution is to update the SQL query to explicitly select a collation method. Another solution is to attempt to change the character set used by the tables, although dependent on encoding, this can result in undesirable side effects. It is unclear why this issue emerged, as collation should have been specified by the database.
Can you suggest what should I do. If I update the query wont the next plugin update overwrite it?
Please advise on how to proceed