Skip to main content
Participant
September 6, 2018
Answered

Since the update - document library errors for our established workflows

  • September 6, 2018
  • 2 replies
  • 660 views

Our users are reporting that they can enter the email information and change the document name for sending using a workflow, however, when they click on send, they are receiving a document library error, and the form will not send.  I also received an error that simply said "Something went wrong.  Please try again after sometime."  On my third or fourth attempt, it finally went through.

We have been using these documents and workflows for almost a year now.  The only change is yesterday's update.  Is there a workaround?  Do I need to open each template and each workflow and re-save them, or remove and re-add the template to the workflow?  Removing and re-adding the document to the workflow is what fixed it for the one I had to send today.

This topic has been closed for replies.
Correct answer AkanchhaS8194121

Hi Jcarlson, 

We apologize for the delay in response to your issue reported.

Are you still experiencing the same problem or looking for the resolution for this? There was an intermittent issue reported after the September release. Which had been rectified and the services were back to up and running.

Hoping the issue has been fixed with a immediate effect.

Let us know if you require any further assistance on the same.

Regards,

Akanchha  

2 replies

AkanchhaS8194121
AkanchhaS8194121Correct answer
Legend
November 28, 2018

Hi Jcarlson, 

We apologize for the delay in response to your issue reported.

Are you still experiencing the same problem or looking for the resolution for this? There was an intermittent issue reported after the September release. Which had been rectified and the services were back to up and running.

Hoping the issue has been fixed with a immediate effect.

Let us know if you require any further assistance on the same.

Regards,

Akanchha  

Participant
September 10, 2018

In case any other users are having this issue, I was informed over the weekend that this is a known issue with the update.  I'm surprised more people haven't reported it.