I have just created a MailChimp Account, then I created a list and added a user, I created a campaign and then selected a template; I edited the template and sent it to the List. But after that I got the following error. Please tell me how to fix this issue as we are on deadline and have to deliver thing in a month.
While exploring the MailChimp API, We came to know that the current connection limit is 10 simultaneous connections per user account. If Limit crosses then error message will be returned.
Is this limit same for free forever plan account and other price plans account?
Kindly let me know the answer.
Thanks
Sonia
Related
When creating Calendar Events via the Graph API, the events are created correctly in the calendar of the organizer but the invites to the participants get bounced. The organizer gets a 'Delivery has failed...' message with the following error message:
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653 AS(7171)
Sending emails manually through Outlook (web) from the organizer to the participants works fine.
The issue is intermittent. After changing the DNS server, everything worked fine for some time.
I checked https://protection.office.com/restrictedusers as suggested in the answers to similar posts, but this list is empty.
I also tried delisting the IP address (my own?) through https://sender.office.com/, but to no avail.
The tenant is linked to the Microsoft Developer Program and would allegedly have a 'bad reputation'. However, I don't understand how that would explain the fact that it sometimes works and sometimes doesn't when sending exactly the same API request and hence 'triggering' exactly the same emails...
I think the best way to overcome this would be to add a domain to your developer tenant as per the guidance here:
https://learn.microsoft.com/en-us/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-5-7-700-through-5-7-750#57750-client-blocked-from-sending-from-unregistered-domain
Add and validate all domains in Office 365 that you use to send email messages. For more information, see Add a domain to Office 365.
I'm not guaranteeing this will resolve it. You have to understand that those developer tenants are only meant for experimentation and so there are checks and balances to ensure they are used in a bad manor.
How many emails are you sending through this tenant?
Calendar events are sent out via email. Add the "Mail.Send" permission to you App Registration.
This solved it for me.
See above mentioned image, it gives different status but don't know how to get it.
Check Outlook API.
Thanks in advance :-)
You can use GET https://outlook.office.com/api/v2.0/me/events/{event_id}?$select=ShowAs to retrieve the FreeBusyStatus of attendee(yourself) for a particular meeting, the return type is something like below,
If you want to check the response from a particular attendee, use GET https://outlook.office.com/api/v2.0/me/events/{event_id}?$select=ShowAs,Attendees, and check on the "Response" from the "Status" response.
This enumeration is used for 'Specifies the availability status of an attendee for a meeting.' At present, the Office 365 REST API is not able to retrieve the contacts' meetings status. And you can submit the feedback from here if you want to the Office 365 REST to support this feature.
We are able to add other’s users’ calendar manually, then we could see the status of the appoint/meet of him/her. Here is an figure that show the others calendar for your reference:
If you want to retrieve the free/busy information of EWS is a possible workaround. Please refer to here for more detail. And if you require these information to schedule a meeting, you can try to use the Find meeting times (preview).
I have an Account wherein 2 Appointments appear in the Activities section. I updated the regarding of those Appointments to point to different Accounts. However, the Appointment still shows in Activities of the Account it belonged to originally. Also, this Appointment shows in the new Regarding Account.
Additionally, the owner of the Account record has been disabled in CRM. Could this be a reason for this? Kindly help.
Thanks.
To change the relation completely, have to change the participants in the appointment as well as the regarding attribute, otherwise it will be related to the original account
Hope it helps - M.Acosta.D
With the release of the new subscription option from In-App Billing API we started a proof of concept of the service and we found a few issues. Has anyone else tried it and would have some answers for us? Here's the issues we have been facing so far:
1 – While testing the unsubscribe functionality, the Google Play interface displays a white page with an “Item not found” message and a retry button. Is it due to the fact the app is not yet published? If yes, how can we test this flow without publishing it first?
2 – Inter device synchronization. When making a subscription on one device, other devices tied to the same account did not receive a OnPurchaseStateChange event. Is it again due to the fact the app is not published? Or are subscriptions tied to a particular device and not to an account?
3 – On our Google merchant page, when we cancel a purchase, the device does not receive a notification telling the subscription has been cancelled. Is this a bug? As a workaround we are manually checking the current time and comparing with the expiration date to force a restore transactions call. At this point, we are able to see the subscription is no longer valid. Do you think this is an acceptable solution?
4 – When a subscription is made, two transactions show up on the Google Merchant page: a FAILED transaction with a value of $0 and a valid one with the value we charged. Is this the expected behavior? What’s the purpose of the $0 FAILED transaction?
If anyone has faced similar issues we would like to know. Maybe these could be bugs on Google's end or maybe we did not understand 100% how it is supposed to work.
Thanks in advance.
1.I had the same issue and after I published (and later unpublished) my app I could see the app page in the market,so you can publish and than unpublish.
2.I didn't check it with subscriptions ,but for managed item i didn't get purchaseStateChange on two different devices as expected.
3.I do get subscription expired after canceling one,but only after a while.
I didn't understood how you can get the expiration date ?
you only can get it with access to play developer api.
the restore transactions will give you same purchaseStateChange as you got when purchase the item.
*in the developer guide it is recommanded to use restore transactions only in first app use.
4.I have same issue,and i heard at least about 10 people with same 0$ charge.
I have set up payment processing through Authorize.net (actually through a reseller) and I am able to successfully perform Test transactions. However, when I perform real transactions, I get a Rejected transaction. When I check the transaction in the authorize.net account I see "General Error (Request rejected by FDC Omaha - Wrong Merchant Type). I assume this is some sort of configuration problem between First Data and authorize.net or me. However, I have no way of telling exactly what the problem is. Authorize.net told me to contact my MSP and the reseller is saying there is nothing they can do to fix the problem (I find it hard to believe.) Is this a setting on my side that I can fix? Help!
You must contact your merchant account provider to fix this error. I've seen this error message several times with our customers at www.authnetscripts.com.
The error indicates a mis-configuration with the processor.
Thanks!
We got this error recently on one of our sites, so we followed the advice to call the merchant account provider.
We called and they told us that sometimes you can get this error because of the type of card (MasterCard, Visa, Discover, AmEx, etc.) that is being used. We tried a different type of card and it processed correctly.
Hopefully that helps someone else who runs into this same problem.