Skip to content

Anonymous

My feedback

3 results found

  1. 29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 
  2. 64 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Our stance still stand on this feature and we still wish to provide it to you guys eventually.

    At this point this is more a question of priority and once we feel like our features to move to the cloud and other environnements are on point, we will get to this.

    Anonymous supported this idea  · 
  3. 52 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Currently, we run or schedule multiple jobs but we have no control if one job is finished before the next starts. If jobs overlap we quickly run into O365 throttling issues. I'd love it if we could queue jobs when using the GUI. That is, when one job is running and we add another job, we get the option to start immediately (just like it is today), or start as soon as the previous job is done (ensuring we only have one running job at a time). With Powershell we already have that if we have multiple Copy-Content operations in a row (it will stay on the first job until completed or only remote processing remains). Now we just need that option for the GUI as well!

Feedback and Knowledge Base