Customer verification for RPA 20.3.2
In case you're running Migration Script after all Services are up, one can fail to edit the trigger (in SEQ, it occurs as Controller logs of a trigger that doesn't exist).
The workaround:
- Stop all the services, including new Console services (currently manually).
- Start all the services, including new Console services.
Correct procedure:
After Upgrade installation, stop all the services include Console services.
- Run Migration script
- Start all the services, include Console services
The reason: The controller does not recognize migrated triggers due to a lack of subscription (during code creation or Controller service up).
https://kryonsystems.atlassian.net/browse/RPA-3483
The workaround is to enter the trigger and edit it from the trigger page: Activate and Save.
