Get informed on conflict or if other manual action needed

[M_Meyer]

Hello,
I would like to get informed if a conflict occurs or if manual delete is needed or if some other error occurs, so every time manual action is needed.
I am running SFFS as background job with SmartTracking and already missed a conflict several times because I was not looking at the result page. So I would like to automate such an information in case of conflict or other error.

I tried "execute after", but this does not seem to be triggered on conflicts, only on "real" errors.
The email options do not seem to be suited either.

So is there a possibility to do this?

Another question: For the execute after commandline, only $LEFT and $RIGHT are valid, but none of the other variables. Is there a plan to extend these?

[superflexible]

Hi,

the SmartTracking conflict action can be set to "Prompt". Please try it. In addition, you can set up your email notifications so that an email is sent upon conflicts and errors.

The command line parameters are extended only upon specific customer requests. Please let me know which variable you need.

[M_Meyer]

I have already set the SmartTracking conflict action to "Prompt".
When manually starting the background job, there is no prompt, but there is a conflict.

I will also try the email notification although I would like to do it via "run after".
The job does not run on a remote computer, it is my workstation, so email seems to be a little bit too much and too indirect for what I want to achieve.

If "run after" would work with conflicts, too, I would like to get $PROFILENAME as parameter into the batch.

By the way, the new sizes in the profiles overview results are very nice!

[superflexible]

Hello,

currently, background jobs are normaly run in a separate thread, and then they can't display any dialog boxes. I will enable them to show conflict prompts in a new version soon.

I will also think about the "Run after" request.

[superflexible]

By the way, background jobs can show a conflict prompt if they are run by the scheduler and the scheduler is not set to "Start profiles in parallel".