I am a little confused at the moment i am trying to charge a credit card in sandbox mode on PayPal's Rest SDK.
When i attempt to take payment i am getting the following response:
{
"status": 500,
"duration_time": 124,
"body": {
"message": "An internal service error occurred.",
"information_link": "https://developer.paypal.com/webapps/developer/docs/api/#INTERNAL_SERVICE_ERROR",
"name": "INTERNAL_SERVICE_ERROR",
"debug_id": "1d327d8a79044"
},
"additional_properties": {},
"header": {
"Content-Length": "209",
"Content-Language": "*",
"X-SLR-RETRY": "500",
"CORRELATION-ID": "1d327d8a79044",
"Date": "Thu, 14 Jul 2016 16:49:14 GMT",
"Connection": "close",
"Paypal-Debug-Id": "1d327d8a79044",
"PROXY_SERVER_INFO": "host\u003dslcsbplatformapiserv3001.slc.paypal.com;threadId\u003d200",
"Content-Type": "application/json"
}
}
I am unable to find anymore information on this, I've searched various places and seen a few suggestions ive tried such as negative testing on/off and that made no difference at all.
Any help would be apreciated,
Regarding "INTERNAL_SERVICE_ERROR", in sandbox environment, the testing credit card in your API request is a generic one and there are lots of accounts attached to this credit card, when PayPal execute your API request, we need to load all the related accounts during transaction, so it caused time out error and internal service error, please try some rarely used card number, such as below:
VISA 16 digit
4916339731576481
4916037567876898
4024007171154213
4532782720397175
4556654893065114
4539432483175995
4716339122298416
4532325401406798
4539157680503828
4124138105007679
4485178251029161
4916231960500037
4058178241644969
Please have a try.
Related
As part of MFA in a custom policy we're using AzureMfaProtocolProvider to send one-time codes via SMS.
For some users we're seeing the following error:
{
"Key": "Exception",
"Value": {
"Kind": "Handled",
"HResult": "80131500",
"Message": "ErrorCodes: UserMessageIfBadReputation",
"Data": {
"IsPolicySpecificError": false
}
}
}
I can't seem to find any information regarding this error in the docs.
How can I figure out what triggers this and why it was triggered for that specific user?
PhoneReputation service is integrated with Azure MFA to provide a near-real time determination which tracks tracks the usage and reputation of phone numbers as they are used across various Microsoft services.
Any particular browser user agent having the issue, few days back i worked on a similar issue where latest version of firefox reported this kind of issue reference: https://learn.microsoft.com/en-us/answers/questions/1090554/azure-b2c-unblock-phone-number.html?childToView=1097185#comment-1097185
Also where are the users located who reported this error ? any specific region/country code users reported this issue.
I'm trying to automatize process using Logic Apps -> On-premises data gateway -> SAP system.
I think I have a problem with metadata or cache.
Scenario:
I stopped developing solution on Wednesday about 23 (it didn't work), I didn't change anything inside and started to work on Thursday (today) about 12. I had to remind myself what kind of bug it was so i ran this logic app and suddenly it worked fine. I've been using element [RFC] Call function in SAP in Logic Apps with input RFC parameters:
<ZFM_MGR_RFC xmlns="http://Microsoft.LobServices.Sap/2007/03/Rfc/">
<INVOICE_ID>#{outputs('Invoice')['InvoiceId']}</INVOICE_ID>
</ZFM_MGR_RFC>
ABAP FM:
IMPORTING
VALUE(INVOICE_DATE) TYPE STRING OPTIONAL
DATA: ls_test TYPE zasd_test.
ls_test-mandt = sy-mandt.
ls_test-dates = sy-datum.
ls_test-time = sy-timlo.
INSERT zasd_test FROM ls_test.
So... I decided to enhance my FM in ABAP with another importing parameters. I added for example CUSTOMER_NAME parameter (string) and input parameter in Logic Apps. Suddenly I have an error - there's my [RFC] Call function in SAP response:
{
"statusCode": 400,
"headers": {
"x-ms-request-id": "7c4b6579-956d-4816-b988-73ad72d2962e",
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"X-Frame-Options": "DENY",
"Cache-Control": "no-store",
"Set-Cookie": "ARRAffinity=db497ba0020393419ac466ef860f11922d2080b57a6df974e13c227f651e3274;Path=/;HttpOnly;Secure;Domain=sap-gwc.azconn-gwc.p.azurewebsites.net,ARRAffinitySameSite=db497ba0020393419ac466ef860f11922d2080b57a6df974e13c227f651e3274;Path=/;HttpOnly;SameSite=None;Secure;Domain=sap-gwc.azconn-gwc.p.azurewebsites.net",
"x-ms-connection-gateway-object-id": "7ebb3fec-1964-41ff-b45b-b97e71c65616",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"Date": "Thu, 15 Jul 2021 21:37:41 GMT",
"Content-Length": "202",
"Content-Type": "application/json"
},
"body": {
"error": {
"code": "GeneralBadRequest",
"message": "Failed to process request. Error details: 'Parameter: 'CUSTOMER_NAME' not found in the function metadata.'.",
"target": ""
}
}
}
It looks like Logic Apps/On-premise gateway has metadata of function module saved somewhere and refresh it not very often. How can I change it?
Thanks in advance.
I found a solution. Inside On-premises data gateway in settings overlap there is "Restart right now" button. Everytime you change something inside configuration/source code of program you have to click this button.
Warning: restarting computer doesn't give the same result. You have to restart gateway manually.
PS If you don't use On-Premise SAP Gateway you can temporarily test your solution with copying one FM to another and running the 2nd one.
Maybe I'm misunderstanding something but every article/tutorial I've read about push notifications seems to be leaving this detail out.
For reference, web-push's sendNotification method accepts pushSubscription, payload, and options.
To send a notification to a user at any point in time, the user's pushSubscription data would need to be stored in a database and retrieved to be used as needed, right? So if the user has enabled push notifications for multiple devices, the pushSubscription data would need to be stored for each device.
I guess my question is... How do you know when e.g. a device is no longer in use so that you can delete the stale pushSubscription data? Or suppose, for whatever reason, the PushManager generates a new pushSubscription for the same user + device... How would you know to replace the old pushSubscription with the new one?
Is the solution to build a device manager for the user to manage each device and its associated push subscription(s)?
I think you have this right -- a nice implementation is one where you show the browser(s) with push notifications enabled. Another way is you just prompt to enable push notifications if they aren't enabled in the current browser in use.
Stale: HTTP 410 Gone
I've found that when a push notification goes away, the push endpoint will return a HTTP 410 Gone status code. So if I get that in response to a push attempt, I remove that push entry.
Microsoft Edge rate limits with HTTP 406
On a side note, I found in practice that the Microsoft Edge push servers will often return a HTTP 406 Not Acceptable status code if you push too many notifications. So in a perfect world, in an app where many notifications were sent, we'd alert the user about that issue. Here is an example of that response:
{
"name": "WebPushError",
"message": "Received unexpected response code",
"statusCode": 406,
"headers": {
"content-length": "0",
"retry-after": "900",
"x-wns-notificationstatus": "appthrottled",
"x-wns-status": "appthrottled",
"x-wns-msg-id": "_redacted_",
"x-wns-debug-trace": "_redacted_",
"ms-cv": "_redacted_.0",
"strict-transport-security": "max-age=31536000; includeSubDomains",
"date": "Fri, 21 Oct 2022 15:55:28 GMT",
"connection": "close"
},
"body": "",
"endpoint": "https://wns2-bl2p.notify.windows.com/w/?token=_redacted_"
}
I was surprised to find there isn't really a lot of solid technical articles about implementing push notifications in the big picture. Once you get into the details, it's not too bad but it is definitely an area which could use more documentation and discussion.
I work on application with Instagram API. Today I have problem with searching users
https://api.instagram.com/v1/users/search?q=john&access_token=6714600555.af81720.58e232564ed94361a8d78a77cfdfce5f
I got this error
{
"meta": {
"code": 400,
"error_type": "APINotFoundError",
"error_message": "this user does not exist"
}
}
Do you know where is problem?
User search was deprecated 4th of April 2018. Many endpoints have been deprecated since the Cambridge Analytica data scandal.
https://www.instagram.com/developer/changelog/
I have followed Instagram documentation (https://www.instagram.com/developer/subscriptions/) on how to create a user subscription.
This is the response that I get after creating the subscription:
{
"meta": {
"code": 200
},
"data": {
"object": "user",
"object_id": null,
"aspect": "media",
"subscription_id": 0,
"callback_url": "http://CALLBACK_URL",
"type": "subscription",
"id": 0
}
}
Some of the users that have authenticated with my app have posted some media and yet I'm not seeing anything from my end, which makes me think that there might be an error with the subscription.
subscription_id or id 0 does not look correct to me. My app is still in Sandbox mode, is this the problem?
Also, I have tried creating another subscription with object=tag and object_id=blah but it returns the same response as above.
Any advice would be very much appreciated. Thank you!
The subscription_id=0 looks weird but it's normal in sandbox. Perhaps you can make sure your callback url is actually receiving the post from Instagram properly (save it to a log to test).