Background Processes in system

[Alexis Sarah]

The following came from an email string regarding some of the background processes that happen in the system.

Thanks to Mika from Rideshare online support and Amol at iCarpool!

-----------------------------------

What are the scheduled background tasks? 

[Mika] Examples of these tasks are:

Inactive users to be deactivated after 180 days

Non-validated user accounts to be removed after 7 days

Reminder to confirm user account after 3 hrs.

Inactivity reminders sent at 50, 100 and 150 days

Remove expired one-time trip after 7 days

I don’t know if this is a comprehensive list or not, I’ll check with iCarpool

[Amol] The AutoLog task logs unconfirmed trips in the user’s account based on the trip template. The Autoclean task removes unconfirmed trips (that were logged based on the trip template), expired events. The Network Statistics task aggregates and updates statistics of  networks (visible in Achievements or My Networks).

 

Are the background tasks carried out by iCarpool or an admin?

[Mika] The tasks are handled by iCarpool; but system settings (# of days) can be changed by a Global administrator (myself and a couple others).

 [Amol] The background tasks are automated and run periodically.

 

I don’t see any reference to Autoclean on the admin live system.

[Mika] This should probably be documented somewhere so all admins know the process.  I’ll mention to Anne.

[Amol] This is an internal system function and isn’t something most administrators would need to use the system.

 

[Mika] I was referring to the fact that Admins should be aware that there is an automatic process that reminds users after 50, 100, 150 days to log into the system to keep their record active.  And, that after 180 days the record is Deactivated – but can always be re-Activated simply by logging into system.  And, that when record is Deactivated all Ridematch trips are removed so they do not appear on matchlists.  Also, information that Vanpools are excluded from this process – reason there are some with old last used system dates.

 

In the live system: Once a user leaves a network, are the trips they logged deleted as well?  (I assume so)

[Mika] If you are referring to past trips in their calendar – no, they are not deleted.  A user can delete, but only within 28 days.

 

In the live system: If a user needs to leave an employer/organization network, but they cannot delete their trips logged because they are too far back---what should the process be for their admin? (contact Rideshareonline support?)

[Mika] No reason to contact us - calendar trips cannot be deleted beyond the 28 days, by anyone. 

[Amol] The user does not have to remove calendar trip logs to leave the network. The user has to remove ride matching trips that use network addresses or worksites of that network. The issue seen on the training site was because Alexis’s account had expired one time ride match trips. This issue will not be seen in the production site because the Autoclean will remove expired records.

[Pamela Blackhorse]

Thanks, Alexis - p