I have a sharepoint list , I have a created a "flow" that says when a new item is added to sharepoint list send notification to my custom powerapps application.
My powerapps notifications are not going through. Below is my error message,
Action 'SendPushNotification' failed
Fix It:
You should be able to fix this by verifying your account with PowerApps Notification. You may need to re-enter your password.
Error type:
This action failed because the connection '-People Advocacy' is not authorized.
Error Details:
The error message from the service is below. This maybe useful for support:
The client certificate was not provided.
Related
Context
Currently we are using Azure Bot Service. The Bot Service is setting up an message endpoint which is directed to our on-pre server
We can successful detect an request coming in when user send something through bot.
But when user edit the previous messages, not request comes in
Message endpoint on Azure
User send a new message on bot
User edit a message on bot
Question
Does there exists a way to receive the update request when users edit their previous messages on bot?
Check out the link mentioned below to verify "Update Activity" section which is nearer to the current requirement.
https://learn.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#update-activity
We are trying to get a callback from DocuSign to our application when an email failed to be delivered to a signer.
So far, we have set up an ‘AutoResponded’ listener, but did not manage to get a callback.
In our developer account admin settings, we have also enabled following settings:
Account > Updates: Send Individual Messages [Switched status to
Active]
See screenshot
Integrations > Connect: In our custom configuration, under
Trigger Events, we have enabled Recipient Delivery Failed See screenshot
Any advise if we need to enable any other setting? Thanks!
There is a setting which needs to be enabled and it is available only in back-end in DocuSign. You need to create a ticket through our support center provide your account number and ask support to enable it.
You need to be admin on the account to request this change
we have an application that is using the Outlook REST API v2 to allow the users to send emails from the app.
Today one of our clients send us a bug report, that after they created a new Office365 account for their company they can't send emails through our app. The current case was for sending email to hotmail.com account. The email bounces back with error code
550 5.7.708 Service unavailable. Access denied, traffic not accepted
from this IP.
The user also reports that they are able to send the same email from the Outlook web client.
I have found this issue on the network: https://social.technet.microsoft.com/Forums/ie/en-US/608d046b-755a-4264-8cdd-fc34c72ccf8f/office-365-tenant-blacklisted-on-all-emails-sent-by-ms-outlook-2016?forum=onlineservicesexchange and am now wondering if this is just a bug on Outlook side or we have missed something on our end?
You have to go here: https://sender.office.com/ and put the incriminate ip to delete it from the list.
I am using a DocuSign Custom Workflow and the DocuSign API. I am always getting an error, Error Description: Could not find a DocuSign User entity for the current user - transaction creation failed. I have tried many ways like refreshing the configuration connection to O365 and assigning the users with the DocuSign User Role. Still we're getting this error. Any idea why?
Here is the screenshot of the DocuSign Workflow.
This is probably because somehow, the association between your CRM user and your DocuSign user got deleted or removed. Try going to a DocuSign enabled entity and clicking "Go To DocuSign" from it ("..." button in the ribbon). That should re-establish the association between CRM and DocuSign. Workflows don't do this automatically for you.
If that does not work, you should get in contact with our customer support because we have a newer version out (4.2) which will allow you to edit the associations between CRM users and DocuSign users.
In our DocuSign Demo environment, we noticed that when several envelopes were voided, we did not receive the corresponding connect events. We checked the connect logs and the envelope ID's are not listed. We checked the envelopes in DocuSign and verified that the envelopes were properly voided. We sent a couple more through and recieved the events successfully.
Has anyone else experienced this issue and if so, were you able to correct it?
I'd suggest you verify the following Connect settings via the DocuSign UI (Preferences >> Connect >> [Connect_Configuration_Name]).
Ensure that Allow Envelope Publish is selected:
Ensure that Envelope Voided is selected, and also that All Users Integrated is selected (assuming you want Connect to send notifications for all envelope void events, i.e., for all Envelope Senders)
Provided that the Connect configuration settings are specified as described above (and logs are enabled via the Enable Log checkbox), you should at least see the Envelope Id in the Connect Log file anytime an envelope is Voided (even if some connectivity issue prevented the message from actually reaching your listener). Also, keep in mind that the Log file only preserves the 100 most recent log file entries -- so if there have been more than 100 messages sent since the Envelope Void that you're looking for in the Connect log, it's expected that you wouldn't see that Envelope Id in the log file.
Working with enterprise support, we determined that our missing connect event problem was caused by using the 'Send on Behalf Of' feature. We were listing the authenticating user in the 'Select Users to Integrate', and needed to list the send on behalf of user.
Also, Require Acknowledgement is NOT mentioned here and can and generally does play into debugging connect issues.
Related article:
Docusign Connect retry frequency when require acknowledgement enabled