| Id: | 20697 |
| Product: | finPOWER Connect |
| Type: | FIX |
| Version: | 4.00.03 |
| Opened: | 18/09/2023 |
| Closed: | 18/09/2023 |
| Released: | 27/09/2023 |
| Job: | J032059 |
 High Importance |
|
HTML Widgets; Background Processes may incorrectly indicate they have "most likely been aborted" if the Script has not added an event entry for 5 minutes
HTML Widgets rely on the Script code continuously notifying the system that it is still running correctly.
This is done via code such as:
mProcessStatus.AddEvent_Information("Report still running", "")
However, there may be places in the Script where the following code is being called (since it doesn't make sense to keep adding events):
mProcessStatus.NotifyProgress(Row / RowCount * 100, "Processing Accounts")The above NotifyProgress call was not notifying the system that the Script was still running and, if the code ran for 5 minutes without adding an event, the User would likely see the following message appear when monitoring the Widget's status:
Status was not updated for 300 seconds indicating that this Background Process has most likely been aborted.
The following changes have been made:
- Calling the
NotifyProgressmethod will now notify the system that the Script was still running - The assumed period of inactivity has been increased from 300 to 600 seconds (10 minutes)
Therefore, if Script code does not call either one of the AddEvent or NotifyProgresss methods, the following message will be returned:
Status was not updated for 600 seconds indicating that this Background Process has most likely been aborted.
NOTE: There is still the risk that the Script may run a SQL query that takes more than 10 minutes to execute. This will be addressed in a future update.