You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found a minor low-priority bug in the universal workspace-setup that we should add to our backlog. Here's the details...
When we run Workspace-Setup, at the end it creates the job "DBAcademy Workspace-Setup" to allow future re-runs of workspace setup. So far so go. But if we then run that job, when that job reaches the part where it creates a job, it doesn't detect that the job already exists, so it deletes the active job and defines a new one. This results in the active job finishing with the result "Canceled" instead of "Completed". All in all this isn't a big deal, as everything does still finish by the time the cancelation finishes taking effect.
The text was updated successfully, but these errors were encountered:
@dougbateman I didn't know that it canceled the current job.
The reason we are deleting it and not updating it is that several parameters cannot be changed with an update. This dictates that we delete it and recreate it.
From @dougbateman:
I found a minor low-priority bug in the universal workspace-setup that we should add to our backlog. Here's the details...
When we run Workspace-Setup, at the end it creates the job "DBAcademy Workspace-Setup" to allow future re-runs of workspace setup. So far so go. But if we then run that job, when that job reaches the part where it creates a job, it doesn't detect that the job already exists, so it deletes the active job and defines a new one. This results in the active job finishing with the result "Canceled" instead of "Completed". All in all this isn't a big deal, as everything does still finish by the time the cancelation finishes taking effect.
The text was updated successfully, but these errors were encountered: