The error is typically related to a hosting/server configuration. You can get some more details by searching online for “curl error 28 meaning” or this post has been helpful for others on the topic here: https://ww.wp.xz.cn/support/topic/curl-error-28-operation-timed-out-after-10000-milliseconds/
In the future, our plan is to modify our background process functionality as we move away from Google Services API to a new cloud print solution architect and overall new solution. In the interim the impact on functionality and overall performance from this error is minimal with only a small reduction in background process performance.
Regarding the impact. This plugin has had a significant impact on site performance, especially on the WP dashboard. Site performance returns to normal after deactivation of plugin.
I noticed in your recommended thread that the users were using Stripe as we are, so, I’m going to check for errors coming from Stripe.
Thanks for the feedback.
A quick update on our side. We did more optimizations to hopefully reduce the risk of the loopback breaking related to the Print API functionality, released in version 3.0.11.
We’ll close this support forum post, but if the issue still persists, please feel free to reopen the post and provide any logs available related to the error on your site.
