"restart" argument to timer commit no longer respected?

Comments

2 comments

  • Avatar
    Hetal Mehta

    Hi Ricardo,

    Thanks for bringing this to our attention.

    I have reported this to our development team and while they look into it, a workaround would be to start a new timer on the task. While I don't have a fixed timeline, we will surely let you know of any update on this matter.

    0
    Comment actions Permalink
  • Avatar
    Ricardo Signes

    I got a private reply that this is a known change that was not announced, but when I clicked the link to Zendesk to reply, I get a 404 error, so I'm here.

    I am pretty disappointed.  That feature was added at my request 4 years ago: https://liquidplanner.zendesk.com/hc/en-us/community/posts/210588277-RFE-simple-commit-work-on-timer-endpoint

    …specifically requested in a way to minimize the number of distinct API calls required to do things.  I will go update our chat bot, but every extra API call means more more possibility that something fails partway through an operation.

    0
    Comment actions Permalink

Please sign in to leave a comment.