I am doing the same thing as yesterday: I fill out form that is connected to the Documents process, I get Forms email but not the end user email from the Documents. AFAIK I didn’t do any changes.
UPDATE: They are in the Payload status. Yesterday they were sent instantly. What should I do?
UPDATE2: Normally it goes through these steps:
Click to download data sent to template. The link is valid for 24 hours.
Applying DOCX template started.
Applying DOCX template finished.
Converting DOCX to PDF started.
Converting DOCX to PDF finished.
Applying test mode watermark started.
Applying test mode watermark finished.
Gmail delivery started.
Gmail delivery finished.
Process finished.
Click to download result document. The link is valid for 24 hours.
And now it stops after 7. I’ve disconnected the Gmail account, revoked Plumsail access on Google side, reconnected the Gmail back making sure that “Send email on your behalf checkbox” and nothing.
UPDATE3: Ok now the one process timed out and I’m getting all the email in a bulk. This was probably caused by the short outage some hours ago. I’m going to test if it works normally now.
I’ve the same identical problem since yesterday night. Support team said me that are investigating and will reply as soon as possible. In the meantime I’m blocked…
Mine is solved. This was probably caused by a short outage but right now it all works just fine. It was just bad luck having server problems in the middle of me working with the templates.
Mine is still no solved. My plumsail document generation process start thanks an action from Zapier. The problem I’m facing is that plumsail generates correctly the document but then the document itself is not available for the further action of Zapier (e.g. upload to a Dropbox folder or send by Gmail). So I can download the generated document only from the specific plumsail log page (within 24 hours) but nothing else.
All these problems started yesterday night when, on my plumsail account, there was an error message “500 internal server error “. This morning still have the error message.
@maratnugmanov Our development team has identified and resolved the issue. The root cause was an abnormally high system load, which led to request timeouts.
@Angelo_Vannutelli For Zapier-based flows, our developers are still working on a fix. This part is still under investigation. We’re continuing the communication with you in the support ticket.