I have a logic app that gets triggered when a new email arrives in a shared mailbox. Seems like trigger is not working when new email is in Inbox.
I created a new connection to the shared mailbox and authorized by myself, but still trigger is not working.
Error is below:
{
"status": 404,
"message": "The specified object was not found in the store., Default folder Inbox not found.\r\nclientRequestId: 697f665b-0967-43a3-ac56-fd1932fd91e6\r\nserviceRequestId: 9ffb5c7e-d6a9-44cc-92e3-17f3cdb7271f",
"error": {
"message": "The specified object was not found in the store., Default folder Inbox not found.",
"code": "ErrorItemNotFound",
"originalMessage": "The specified object was not found in the store., Default folder Inbox not found."
},
"source": "somesource"
}
Could you please let me know what permission my id should have on the shared mailbox to authorize the connection. Also, any other suggestion on how to fix this error?
After reproducing from my end, I have observed that you receive this error when the trigger connection that you have given doesn't have enough permissions or isn't a valid Mailbox address.
Below are the few ways that can make this work
Make sure you provide a valid Mailbox Address. If trying to provide dynamically, either try manually providing Folder name or Mailbox Address.
Make sure you wait for 1 day after your account has been added to shared mailbox and given enough permissions.
After providing the mailbox address manually, I could able to view folders without any error.
Related
I have embedded signing configured in a Salesforce community. The whole signing process works(i.e. envelope is sent and signed), but there are some field updates that I configured within the Envelope Template that are not working. I noticed new DocuSign log entries with the following error message - Cannot perform data updates because source ID is undefined for envelope
I'm not sure how the source ID is missing because my envelope gets sent to the right SF contact and the signed document is attached to the contact record.
I followed the instructions here to create a Lightning Component to launch the embedded signing session - https://developers.docusign.com/docs/salesforce/how-to/embedded-sending-signing/
I thought the problem might due to this line of code because mySourceId is not being set anywhere.
new dfsle.Entity(mySourceId)
I modified the code so that mySourceId is set to the Id of the contact. Unfortunately that did not solve the problem. What am I missing here?
My requirement to show all the calendar events of my wishlisted user in my Canvas App. To access the graph API, I have done App registration in AAD with Calendar.Read and User.Read permission.
Using the Client and Secret received from the registered app, Power Apps Custom Connector is created. While Testing the Custom Connector, I am getting the below error.
{
"error": {
"code": "ErrorAccessDenied",
"message": "Access is denied. Check credentials and try again."
}
}
On Analysis:
Scenario 1 : Calendar.Read - Delegated Permission Type
Api - https://graph.microsoft.com/v1.0/users/{UserID}/events
When Delegated permission is given , I am able to access and response from the calendar event API only when the UserID is mine.
But it is throwing the above mentioned error for other users (This is the actual requirement)
Scenario 2 : Calendar.Read - Application Permission Type
Api - https://graph.microsoft.com/v1.0/users/{UserID}/events
When Application permission is given , it is failing and throwing the same error.
First, Will I be able to get other user's calendar event?
What are the steps to be taken to access?
What permission type should be considered for my scenario?
Am I missing any basic settings?
Please advice. I have lost my time for this requirement.
Thanks in advance
If you where to use Delegates permission (which sounds wrong for the authentication flow you want to use) then to access another users calendar (that you have been delegated rights to either via Outlook or the Mailbox Permissions) you will need (Calendars.Read.Shared or Calendars.ReadWrite.Shared) see https://learn.microsoft.com/en-us/graph/outlook-get-shared-events-calendars
For the client credentials flow https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow which it sounds like what you want to use ? then the Calendar.Read should be enough to access the calendar if your doing anything else in the Directory then User.Read will also need to be an application permission. You probably need to look at https://support.microsoft.com/en-us/topic/verifying-oauth-configuration-for-custom-connectors-d733fdb9-6108-4199-b4f5-06e99b02d10f to do some debugging to see what actually happening with your token generation process, you can the use something like jwt.io to check the correct scopes etc.
My company has an application that was verified through the Google OAuth Review/Verification process and is listed as "Published" in the Cloud Console; however, end users are starting to receive the "This app isn't verified" warning when needing to re-authorize.
We tried emailing them Google Cloud Platform/API Trust & Safety Team directly but immediately received the reply "Please note that your email was not received because api-dev-oauth-verification#google.com is not a monitored alias."
Since the application is verified in the console, the "Submit for verification" button is greyed out so we can't contact them that way and we don't want to modify the scopes to require verification again as we want to preserve everything so Google can investigate it in its current state.
That's why I'm reaching out here:
Has anyone experienced this before and have any ideas what could be the cause?
Anyone know a way to reach the Google Cloud Platform/API Trust & Safety Team without the use of "Submit for verification" button?
You are receiving the "api-dev-oauth-verification#google.com is not a monitored alias." message because the address you are trying to send the email to, is a bit wrong.
The correct address to contact the trust and safety team is:
**
api-oauth-dev-verification#google.com
**
Remember that only the project owner should contact the T&S team.
I hit the below error when trying to insert the permission
"code": 403,
"message": "The authenticated user has not granted the app xxx write access to the child file xxx, which would be affected by the operation on the parent"
Here is what I am doing
We have two Google Account,
1. API Account - we used to create folder and change the ownership to Business account
2. Business Account - upload a file
now we try to share to folder to customer and we hit the above error
And here I using OAuth 2.0 Installed Applications to get the access token.
Please advise what is wrong I am doing here
I had the same issue but I realize that its because of the scope for credential wasn't setup properly. I only had DriveScopes.DRIVE_METADATA set which was not enough for downloading files. Once I added DriveScopes.DRIVE_FILE, DriveScopes.DRIVE, and DriveScopes.DRIVE_APPDATA, I was able to download the file without any problem. Hope this helps.
P.S. if you are changing credentials, you have to delete the previously saved credential file.
Based on the Official Google Documentation you received '403: The user has not granted the app' because the request is not on the ACL for the file. The user never explicitly opened the file with this Drive app.
It is highly recommended to use Google Open Picker and prompt the user to open the file or direct the user to Drive to open the file with the app.
I have several clients. All of them are able to retrieve their domain_public user information via directory api using their own credential. Then, one of the client always return a resource not found error even the account is valid. However, when I tried with an admin user with admin_view, everything work fine. Only domain_public viewType return error. Anybody have this issue?
Please confirm that contact sharing is enabled for the domain:
https://support.google.com/a/answer/60218?hl=en
As well as for the user they are attempting to retrieve:
https://support.google.com/a/answer/1285988