Since the installation of Openntf Domino API V10 I am receiving lots of logging messages.
HTTP JVM: Evaluating a formula: " "
HTTP JVM: Completed a formula in 0ms: " "
Does anyone know if this is related or just a coincidence. There is nothing in my developments to produce this string.
We've just been notified of it on Slack, along with the commit that added this. A debug variable was inadvertently left at true. Please look for an updated release shortly.
Related
I'm trying to create a webhook that updates the envelope on my system, but I'm having this issue:
Docusign Issue
Has anyone ever had something similar?
I took a look about this error and I found a bug with connect from last year where there was a special character in the document causing the error. In one of the examples, there was a newline character in the name of the document which caused the error. I would suggest creating a case on the DocuSign support site for further investigation (support.docusign.com).
An internal issue ticket has been opened on this matter. When you do contact DocuSign Support, please reference issue number EC-4887.
For the past several months I have a native iOS application that uses the embedded signing API to generate an embedded signing URL. My parameter for returnUrl uses a URL with a custom scheme, say, for example, foo. I was using this custom scheme to intercept when the signing is complete and transition to another part of my application. This is now broken and get the following response:
{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. 'returnUrl' parameter must be an absolute URL."
}
When I try using the schemes http or https the request works just fine. For example:
https://docusign/complete works
http://docusign/complete works
foo://docusign/complete broken
bar://docusign/complete broken
This is in the dev sandbox and I am not aware of this being broken in production. Is this change intentional or a bug? If intentional, why are you breaking the behavior of the client being able to choose their own URL for redirection? Using this custom scheme, I am able to unequivocally determine that my application is responding to a completion event, without having to introspect any other parts of the URL.
This breaking change is a bug that was introduced by mistake. Thank you for your report on it. I'm escalating it.
This issue is now tracked internally as DocuSign IM-32736
Please contact DocuSign customer support and ask them to add your contact information to IM-32736. Thank you.
This bug has now been declared as a release blocker. It will not go to production. The bug is being fixed and tested. It will probably arrive on demo.docusign.net sometime on Friday. I will update this answer as more progress is made.
Update
The bug has been fixed and the fix has been pushed to demo.docusign.net.
Please advise if this is still an issue. Thank you again for reporting it.
Can anyone help.
I’m using the rest api to create an envelope, and then configure it using the api sender view call (/restapi/v2/accounts//envelopes//views/sender) to get the DocuSign UI.
Creating the envelope and viewing it the first time using sender view to bring up the docusign api works fine.
The problem occurs if instead of sending the envelope I click ‘save as draft’. When I try to go back to the envelope and view it again using sender view I get the following error with http status of 400:
{
"errorCode": "EDIT_LOCK_ENVELOPE_LOCKED",
"message": "The envelope is locked. The lock must be released before requesting the sender token for envelope, id = xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx."
}
The lock seems to wear off after time (apprx 20 mins). However after it wears off I can only view the item once, and then the lock is reapplied.
I can’t find anything in DocuSign api documentation that relates to this behaviour. Any help would be appreciated.
UPDATE (12/Feb/15): This error only happens on my demo account but not on production, so it seems like it's an account setting, but I can't figure out what/where the setting is.
Thanks,
Nick
Yes - there is new documentation about this envelope locking feature and behavior in the February service pack (PDF) available here: https://www.docusign.com/support/releases.
We have a bug logged on our side where Save Draft isn't correctly releasing the lock on the envelope. We should have a fix for this issue in our DEMO environment soon. The locking feature is currently only "ON" in our DEMO environment but not in our Production environments while we find and fix potential issues such as the one identified here. More information about locking is in our February service pack (PDF) release notes available here: https://www.docusign.com/support/releases.
With logstash releasing version 1.2.1, there is an email output now.
in the specs for it, it states that it will send an email when any event is recieved doc
is there a away to use grok to state that if the message contains 'some bad event' that it will send an email as well as send to elastic search?
found an example in the older version. example
With the match feature deprecated, just swap out using the conditional processing. link
I had the snooze app script working on gmail for some time but it seems that after converting to google drive, the spreadsheet vanished (not in trash) and I get emails every night telling me that my script "Not Found" failed to finish successfully etc etc.
The Error message is that a server error occurred - not particularly informative and any attempt to view triggers results in the same error.
Is there any way to get rid of these messages apart from setting up some kind of filter which is counter intuitive as if I decide to run other scripts I may want to see the output.
Thanks
Darren
Darren, can you please raise this on the Apps Script issue tracker: http://code.google.com/p/google-apps-script-issues/issues/list? If possible, please also let us know in the issue tracker request what the email address is where you're receiving the failure notification email.