petergats wrote:Whn i click on log file in the right click menu it tells me none is available, and I assume from searching this forum tht the log will not be available until after the job completes
Correct - it's in memory/temp files/scan database right now. It will be compiled at run end (or Stop)
petergats wrote:...1 error (red number on top of completed files)
If you click (or right-click, I forget exactly, and hard to simulate easily to check) on that red error count, it will open a temp pop-up text file that will list the error(s) so far. It does sound as though that profile is stuck for some reason, but without debugging having been set already, we probably can't tell you why unless the standard log gives any clues (ditto the popup error message). You may have to try and Stop that profile. If it resists (Stop does nothing) it may of course need a task-kill of the whole program from Task Manager, but you presumably want to wait till the other profile ends before you do so. TBH, it doesn't sound as though it's doing much harm even if stuck.
Each profile runs in its own thread, but we don't actually recommend (see contextual Help on Groups, for example) running high-load profiles in parallel anyway (chances are they are contending for something, even if only the NIC). You might want to consider running them in series, at least until you get the Azure container front-loaded. Creating a Group, putting the profiles in it and running (Scheduling,etc) the Group will run them sequentially by default without you needing to hand-start the 2nd one, try and guess/set 'follow-on' timings, etc.