Delete Guests Task Does not Delete Guests

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
The "Delete Guests" task is enabled for every 600 seconds. According to "Last start date", "Last end date" and "Last run date" everything looks like it is running. However, guest accounts with NO carts attached to them are not deleted. Even if I run the scheduled task manually, the guest accounts are not deleted. The only way I can delete the guest accounts is to use the maintenance task. But then they start to pile up again the next day.

The guest accounts are being created by our monitoring service to check if the site is up or not. This opens a tcp connection to port 80. Is the way the connection is being established somehow bypassing some criteria that the scheduled task is looking for to delete the accounts? A user agent or something?

I have commented on the thread below but felt necessary to create a bug report since the feature does not work in my case. I am using a clean install of 3.9.

Thousands of empty customer records created every day
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx?p=5#188177
6 years ago
If your "monitoring service" is doing a GET, then try a HEAD instead.

I thin the sched task should work.  You'd have to debug the code to see why it isn't.
6 years ago
New York wrote:
If your "monitoring service" is doing a GET, then try a HEAD instead.

I thin the sched task should work.  You'd have to debug the code to see why it isn't.


The site is HTTPS, so using a HEAD request is impossible.

I don't know how to "debug" the source code unfortunately.

Regards
6 years ago
I installed a fresh copy of nopcommerce. Ok, so now I have two installations where the scheduled task to delete guest accounts with no cart does not work. Neither by the schedule or manually.

One of two things are happening here. Either the task does not work and it is a bug. Or I am somehow misunderstanding what the task actually does.

When I go to customers and search role by guests, I see guest accounts. When I run the task and go back to customers, they are still there. Task succeeds but guests are not deleted.

This is not rocket science.

Regards
6 years ago
usauto wrote:
The "Delete Guests" task is enabled for every 600 seconds. According to "Last start date", "Last end date" and "Last run date" everything looks like it is running. However, guest accounts with NO carts attached to them are not deleted. Even if I run the scheduled task manually, the guest accounts are not deleted. The only way I can delete the guest accounts is to use the maintenance task. But then they start to pile up again the next day.

The guest accounts are being created by our monitoring service to check if the site is up or not. This opens a tcp connection to port 80. Is the way the connection is being established somehow bypassing some criteria that the scheduled task is looking for to delete the accounts? A user agent or something?

I have commented on the thread below but felt necessary to create a bug report since the feature does not work in my case. I am using a clean install of 3.9.

Thousands of empty customer records created every day
https://www.nopcommerce.com/boards/t/32088/thousands-of-empty-customer-records-created-every-day.aspx?p=5#188177


Having the same problem, like other related post, I don't know if is not happening to everyone, or they don't know that they have the problem. But something is going on because the schedule task says that it runs ok, but the gest register are still there..

Of course no answer by admins.. Pretty way of putting in a good way Nopcommerce...
4 years ago
I am experiencing the same issue with Delete Guests. The problem is how fast they add up. I figure it has to be Search Bots hitting the site and that hit counting as a guest. There should be some way to ignore search bots IP addresses and using them as a Guest. So far no answer to this issue?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.