Reuse of customer for scheduled tasks!

At the moment (v3.8) each scheduled task is creating a new customer (with role background task as far as I can see). As we created over 4.000.000 customer accounts within a year of testing and development, the count of new customers in live system would be much much higher.

As this is somehow unnecessary, can you please consider to reuse only one system account for scheduled tasks? So it would be even possible to identify scheduled task requests and skip some parts of the request (for example statistics).

Hi Sven,

No, they don't create a new customer record (out of the box). It uses the same built-in system customer with "[email protected]" email

Please also note that there's no role such as "background task"

Mmh okay. If that is the case it's as it should be :-) Thank you.

a.m. wrote:


What is the IsBackgroundTaskAccount() method of customer for?

[email protected] wrote:
It checks if a Customer record is the built in background task Customer that Andrei mentioned above. A search of the source code shows that the only place it's currently used is in the RegisterCustomer function of the CustomerRegistrationService to prevent the background task account from being registered.

a.m. wrote:

I looked into this case a bit deeper. As far as I can see there is a guest customer account created for each scheduled task run. So our Ids are increasing very fast in customer table.

Also there is no customer with [email protected] email (SELECT * FROM Customer c WHERE c.Email = '[email protected]').

Is there something missing in our installation or is there a misunderstanding or even a bug?

Okay. One of our developers deleted ALL entries in customer table to import existing customers. That was a fault and I recovered the both built-in accounts for search engines and background tasks. This explains why there are so many guest accounts created.