THE INFORMATION IN THIS ARTICLE APPLIES TO:
- EFT 184.108.40.206, EFT, v7.4.9, and EFT 220.127.116.11
Between EFT 18.104.22.168 and 22.214.171.124, a bug was introduced in which manually imported event rules using the Import Event Rule option will be imported correctly in memory and displayed in the EFT Admin UI. However, the event rule is saved incorrectly in the configuration. The issue will be apparent and shown as soon as the EFT Service restarts, as the event rule will now be treated as a remote event rule. This issue will cause rules to be inoperable and not triggered nor trigger as remote event rules as there is no remote agent associated with them.
This issue doesn’t affect any event rules created manually from scratch. The bug was fixed in EFT 126.96.36.199 and higher. However, upgrading to a newer version will not fix the event rules already imported and saved incorrectly in the configuration. They will show up as remote event rules even after the upgrade.
This behavior can be verified by querying the EventRules.db using SQLite browser. The column IsRemote should be 0 for normal event rules and 1 for remote event rules, however, they are saved with a different random number.
A simple workaround is to update the IsRemote column back to 0 for normal event rules that its value is different than 0 and 1 (random value).
The following SQL Query can show the event rules affected after the restart.
Select * from EventRule where isRemote <> 0 and isRemote<> 1
You can update manually one by one using SQLIte Browser UI or use the following SQL query to update all of them:
Update EventRule Set isRemote = 0 where isRemote <> 0 and isRemote<> 1
Once the changes are done, make sure you commit your changes to the DB by clicking “Write Changes”. Restart EFT and you should be able to see that the event rules won’t be converted anymore.