Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Status Completed
Created by Guest
Created on Jan 1, 2018

The ablity to rerun a workflow, especially one that starts from a form

I had a workflow that failed from a form start and had no way to restart the workflow or retrieve the information that had been entered into the form. Once I fixed the error in my connections, I couldn't rerun it. I also couldn't access the initial information in the form. The data the user had entered is lost and I can't track down any information about what was submitted.
  • ADMIN RESPONSE
    Sep 7, 2022
    You can now resubmit previously failed or completed workflows via the instances page, workflow tracking for business owners and individual forms via My Nintex.
  • Attach files
  • Guest
    Reply
    |
    Sep 7, 2022
    Hi Kate, any ETA on this?
  • Isaiah
    Reply
    |
    Sep 7, 2022
    This is starting to become a pain point for us the more workflows we push out, any updates?
  • Guest
    Reply
    |
    Sep 7, 2022
    This would be extremely helpful to us. Any updates on if it is on the roadmap?
  • Guest
    Reply
    |
    Sep 7, 2022
    The ability to restart / resume a failed workflow instance once the workflow has been updated and republished is a really needed feature. It would also be very useful if workflow variables could be adjusted prior to restarting / resuming the workflow.
  • Guest
    Reply
    |
    Sep 7, 2022
    Would like to restart the workflow from within a workflow instance, so it does not need to be terminated and restarted from the beginning.

    ref:_00D90q6Cb._5002v2Ytg1v:ref
  • Yukiko Yasuda
    Reply
    |
    Sep 7, 2022
    Thanks for your feedback.
    Just to avoid the misunderstanding, I would like to rephrase the word "Restart" to "Resume".
    When the workflow is failed, we want to "resume" it from the point where it's failed, not starting all over again.
  • Guest
    Reply
    |
    Sep 7, 2022
    Noted on the Restart to Resume - it will depend on the error state of the workflow - IF purely resuming due to time out issue, then for sure. But if the value being used in the action configuration requires updates? This may require more thought.
  • Yukiko Yasuda
    Reply
    |
    Sep 7, 2022
    Thanks for your comment.

    >But if the value being used in the action configuration requires updates? This may require more thought.

    -->I'm not sure what you meant this point, but what we are asking is to be able to resume the workflow, not all the failed instances but those which were failed due to HTTP429 error like throttling and/or due to time-out error for some reasons while connecting.
  • Andrew Blinco
    Reply
    |
    Sep 7, 2022
    Hi Rick, I have a specific requirement. A task is assigned to a user who is not a user in Nintex causing it to fail. We need to manually add the user as a participant and then restart the workflow.
  • Guest
    Reply
    |
    Sep 7, 2022
    Hi Rick.

    Workflows fail from time to time. Having the ability to resubmit the start data directly from NWC would be really helpful. It is especially tedious if the workflow is a component workflow with start variables or the workflow starts with a form.
  • Yukiko Yasuda
    Reply
    |
    Sep 7, 2022
    When the workflow is suspended, we can see the instance details from "Instances" tab, but there is no function to restart the workflow.
    It would be good to have a restart function, at least, when it's failed in SharePoint connector such as HTTP429 error or 9min time-out.
  • Guest
    Reply
    |
    Sep 7, 2022
    Hi Rick,

    Critical from my perspective to have that. We've had credentials for a sharepoint connector expire today (and I can imagine we'd have connection issues/outages unrelated to credentials from time to time).

    We just need to be able to restart the Workflow from the point it failed once an issue like that is resolved. Happy to chat further if you still want.
  • Guest
    Reply
    |
    Sep 7, 2022
    Error Handling in WFC. We need a way to handle errors in WFC. Having critical workflows crashing and having to restart them is a huge issue and can cost lots of time and money for the organization.
  • Nicholas Kotze
    Reply
    |
    Sep 7, 2022
    Hi, do we know if this is likely to be available anytime 2022? Deal breaker for a present customer who would like to work with NWC. Three extra votes from me :)
  • Hitoshi Inoue
    Reply
    |
    Sep 7, 2022
    1.We want the same level of function that is given on Nintex Workflow for Office 365 which is able to resume the worklfow when suspended by error.
    2.We want to resume the workflow from the action that gets suspended when it's failed by time-out error (due to the throttling of SPO).
    3.When the workflow is failed because of the user not registered in Nintex and failed in "Assign the task", we want to manually add the user as a participant and want to resume the workflow from the action that gets suspended.
  • Laura Stein
    Reply
    |
    Sep 7, 2022
    This is incredibly important. I have workflows failing because we are changing logins to a different domain (same forest, same O365 tenant) A workflow starts, and then a user who gets a task from that workflow has their login/email changed. When the workflow sends email or a task to the user who changed login/email it fails.
    1. Start workflow with tasks/emails
    2. A task recipient changes login/email before their task is assigned
    3. Task is assigned to them and the workflow fails

    Need to restart the workflow, need the original submitter's name from the workflow, so now have to ask the submitter to submit again. I have to cobble together screen shots of the original form (the data tab copy/paste is not a table, too hard to clean up) to give them. Not a good look. Please help.
  • Laura Stein
    Reply
    |
    Sep 7, 2022
    @Rick De Marco - I'd love to have a chat with you about this.
  • Kerrie Boyd
    Reply
    |
    Sep 7, 2022
    The ability to restart a failed workflow is critical. I'm super excited this has started!
  • Guest
    Reply
    |
    Sep 7, 2022
    resubmitting in the backend it as it was originally submitted is often a quick and easy fix compared to going back to the original submitter to resubmit on a form.
  • Guest
    Reply
    |
    Sep 7, 2022
    Does this also work for component workflows?