Best way to start job sequence

[M_Meyer]

Hi,

I am running several jobs that are started manually (not via timer).
My commandline is
C:\Programme\Syncovery\Syncovery.exe /RUNX=Backup* /M /T /P
This works; the jobs are executed in sequence and the result is reported back to the application.
But: During the run, Syncovery is unresponsive.
I cannot stop the jobs, I cannot see progress during the job execution (as when started from within the application), the app even errors out when closing it to stop the jobs (EAccess violation...).

So is there another possibility to run a job sequence from commandline/batch AND keep Syncovery responsive, reporting the full progress?
Or do I have to use "Run checked profiles in Background"?

[superflexible]

These parameters are meant for SyncoveryService.exe, not Syncovery.exe. With Syncovery.exe you need to leave away the /T and /P.

And maybe you want just /U for unattended rather than /M for minimized?

/T and /P can only be used with the background exe, i.e. SyncoveryService.exe. /T means that the job is run in a separate thread and /P means that progress info is sent to the GUI.

[M_Meyer]

Ah, okay, I see. I just changed the settings from SFFS and did not see the new SyncoveryService.
But when trying the settings with SyncoveryService, nothing happens.
I see SyncoveryService.exe for a short time in the task manager, but no progress is reported and no files are copied.
Do I need to start the scheduler?
What am I missing?

[superflexible]

SyncoveryService.exe does not accept wild cards, i.e. the * does not work. So it did not find any profiles to run. You need to specify the full names in multiple /RUNX= parameters.

It is the same as it was with Superflexible and ExtremeSync.

[M_Meyer]

Okay, when adding the full names, it works pretty cool with SyncoveryService.exe and multiple /RUNX parameters.
With this, the jobs even run in parallel (other than with Syncovery.exe which runs them one after another).
AND an open Syncovery GUI stays responsive - great!

It would be nice to have the wildcard option for SyncoveryService.exe, too.
Is this planned? I did not find this restriction at http://www.syncovery.com/command-line/
Without this, you have to keep track of renamed or added profiles in the calling commandline/batch.

One more remark: When running Syncovery.exe /M, it opens without any profiles shown.
You have to stay cool and switch the tabs to scheduler and back to see the profiles again.

[superflexible]

Hello,

version 6.01 takes care of these things now.

Cheers,
Tobias

[M_Meyer]

Now all this works great, thanks!

[M_Meyer]

Now I saw one remaining glitch:

The wildcard job start (Syncovery) now includes disabled profiles.
This leads to errors because my disabled profiles are not fully tested/functional.
The wildcard job start (SFFS) did not include disabled profiles.

Is this intended?

[M_Meyer]

Any news on this "wildcard job starts disabled profiles" ?

[superflexible]

The difference is not between software versions but between Syncovery.exe and SyncoveryService.exe. It will fixed in the next update!