Resolution when Triggers do not start and Queue section numbers are all at 0.
Issue Description:
Possible scenario:
Robots are not triggered correctly through the Orchestrator, even though the triggers show correctly in the DB.
Both the application server IIS and the SQL server have been restarted with no effect. All of the queue tables were unresponsive from the DB itself and the IISReset does not fix the issue.
Eventually the queue came back and became visible for the user, but they now all display the number zero for everything. How to proceed?
Resolution:
Note: Backup old database. Restore under a different name.
- Change the connection string in the following files to point from the old database to the new database:
- UiPath.Orchestrator.dll.json.
- identity/appsettings.Production.json
- webhooks/appsettings.Production.json
- Restart IIS (run command IISReset in CMD or Powershell)
- Check if triggers are running again.