Hello there,

Thank you for reaching out to us.

Can you please check in WordPress users if you have several roles added to this user? For example admin and employee or employee and customer. etc. Or if this user has the same mail as other user for example admin/manager and employee or employee and customer. etc.

If this is the case then you should know you can not be Admin and manager to admin and employee, etc at the same time since this leads to conflict within the plugin. You need to have only one role per user only admin or only manager or only employee. Every role has different permission and if you combine them Amelia can not function properly.

You need to disconnect other roles from that user and that mail and to create a separate user with separate mail for each role and make sure to purge the cache afterward.

After that Amelia should work properly again. Please do that and let us know how it goes. 

Looking forward to your reply. 

Hello again,

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Hello again,

We will take a look at this now and we will reach out to you again on this ticket as soon as we have more information. 

Hello again,

You have this error

​We will forward this to our Dev team and as soon as we receive feedback from them we will reach out to you again on this ticket. 

Hello again,

We just got the feedback from our colleagues and they have told us that we have deleted this employee directly via the database. It most likely could not be deleted through the application due to some MySQL server setup restrictions. Since you have more than 10,000 appointments in your database, checking whether this employee was connected to any of them caused the SQL query to time out due to these restrictions.

We attempted to simulate this action in our local environment with the same amount of data, and the process completed without any issues. We also tried replicating some aspects of your setup to reproduce the issue but were unsuccessful.

We wish you all the best and hope you have a wonderful day ahead.