FAQs and Troubleshooting
Exporting Delegate Logs
In some situations, Milyli Support may request that you share the error logs with us. To download the error logs, navigate to the Delegate Admin Tab and select the Delegate Settings tab.
At the bottom of the page is a button that can be used to export the logs from the system error table for both Web functionality and Agent functionality.
Frequently Asked Questions
- What happens when the resource referenced by a step is deleted before the automated workflow is run manually?
- What happens if a resource referenced by a step is deleted before the step is executed while an automation is currently running?
- What happens if a resource referenced by a step is run manually outside of the automated workflow and is already running when the workflow gets to that step?
- What happens if someone stops a Relativity resource manually while the automated workflow is on a step for that resource?
- What happens if the Relativity resource referenced by a step was already run and is in an errored state before the workflow gets to that step?
- What happens if I start multiple workflows at the same time?
- Can I use two resource pools, each with their own agent and worker servers, analytics servers, worker manager server, and to run two automations simultaneously? Will they interfere with each other?
- What happens if we add a second Delegate agent?
- What happens if we can’t figure out why an automated workflow has stopped unexpectedly?
- What happens if my agent server goes down for an extended period?
What happens when the resource referenced by a step is deleted before the automated workflow is run manually?
Every time a user attempts to run a workflow, the workflow is validated. If a resource has been removed from Relativity, the user will be notified immediately to reconfigure the step.
What happens if a resource referenced by a step is deleted before the step is executed while an automation is currently running?
When Delegate gets to that step, the step will error, and the workflow will be paused based on step configuration. See the section above about paused workflows for next steps.
What happens if a resource referenced by a step is run manually outside of the automated workflow and is already running when the workflow gets to that step?
Delegate will wait for the current resource execution to complete and then trigger the run again. For example, an imaging set is currently imaging documents. The workflow is configured to run that same imaging set as a step in the workflow. The workflow runs, gets to this step, and sees that it is already running. The workflow will wait for execution to be completed and then queue the imaging set to run. This process allows Delegate to be defensive even when accidental runs occur within the workspace. While this results in additional execution time, it ensures peace of mind knowing that it will get to the next step.
What happens if someone stops a Relativity resource manually while the automated workflow is on a step for that resource?
The step will enter an errored state and the workflow will be paused based on the step configuration. See the section above about paused workflows for next steps.
What happens if the Relativity resource referenced by a step was already run and is in an errored state before the workflow gets to that step?
The automated workflow will disregard the errored state and attempt to run the resource with the configured settings.
What happens if I start multiple workflows at the same time?
Delegate will initialize and enqueue the resource for the first step of each workflow. If these workflows share resources or queues in Relativity, Relativity will remain responsible for determining priority and managing the queue. Delegate will continue to monitor the status of the resource until it completes and then automatically advance to the next step.
Can I use two resource pools, each with their own agent and worker servers, analytics servers, worker manager server, and to run two automations simultaneously? Will they interfere with each other?
The short answer is, both workflows will run simultaneously on the correct infrastructure and Delegate will not be impacted. Delegate is made with this scenario in mind! Delegate will respect the separation of work across resource pools with no additional setup or configuration.
What happens if we add a second Delegate agent?
Adding a second Delegate agent will provide little value. That said, if a second agent is added it will not interfere with the existing one. Delegate has a global rate limit restricting how often the database is accessed via our agents, preventing unnecessary strain on your SQL servers.
What happens if we can’t figure out why an automated workflow has stopped unexpectedly?
While we have tried to account for as many errors as possible and provide as much information as possible, infrastructure issues can still happen. If it seems like Delegate has failed and not the underlying Relativity resource, reach out to our support team by emailing support@milyli.com and include the exported system log with screenshots of the issue.
What happens if my agent server goes down for an extended period?
As soon as the agent server is brought back online, Delegate will pick up right where it left off. At the next check-in, the agent will execute the last tasks that were enqueued prior to the agent server going offline. If the state of the underlying resource has changed, the workflow will react appropriately.
If the resource has finished, Delegate will move to the next step. If it is still running, it will continue to check its status. If the resource has failed, it will respect the steps configured error configuration and either pause or continue the workflow.