Can we somehow (through the API maybe) delete an item revisions? We really don't need more than 10 revisions per item.
It would avoid getting this irreversible error:
[13-Sep-2018 14:00:13 America/Montreal] PHP Fatal error: Uncaught PodioBadRequestError: "This item has exceeded the maximum number of revisions."
Request URL: http://api.podio.com/item/499294283
The number of revisions per Podio item is limited to 5000, and currently, there is no way of removing the old revisions yet.
Related
When calling a remote function on BigQuery, I get the following error The maximum total size of all input parameters is 5242880 bytes.. This error is undocumented (or my Googling ability is lacking). It is even more unexpected as the query that pop this error is as simple as it gets:
SELECT
`remote_function`( payload ) AS results
FROM
`source_table`
The error is definitely on BQ's side, as no error is observed on the cloud-function called.
How to proceed on such issue, I'm guessing I hitting some kind of limit related to remote functions, but which one?
When calling People API's endpoints, especially in Batch requests, we're getting many different types of error responses.
Some have useful explanation in the error message, like:
Quota exceeded for quota metric 'Daily Contact Writes (Batch requests
cost 200 quota)' and limit 'Daily Contact Writes (Batch requests cost
200 quota) per day per user' of service 'people.googleapis.com' for
consumer 'project_number:XXX'.
Which you can detect and properly handle, e.g. wait for 24 hours before retrying that request, but some are more cryptic, such as:
Resource has been exhausted (e.g. check quota).
This does mention rate-limiting, but for which quota? Is it per-user or per GCP project? When can we retry this?
Note that we're getting this for the first batch call when syncing a user account, so I'm guessing this is not per-user quota, but there's no mention of such rate-limits in the docs.
Specifically, having issues handling:
"Sync quota exceeded"
"Resource has been exhausted (e.g. check quota)"
"MY_CONTACTS_OVERFLOW_COUNT"
Here's what I have so far, feel free to edit this answer to add more insights:
Authentication or Google backend issues:
"invalid_grant": bad access token
"Insufficient Permission": access token doesn't contain required scope
"The service is currently unavailable.": Google issue
"Internal error encountered.": Google issue
"Authentication backend unavailable.": Google issue
Quota and rate-limiting:
"Sync quota exceeded": ???
"Quota exceeded for quota metric X": A specific quota had been exceeded (per min / daily will be part of the message)
"Resource has been exhausted (e.g. check quota)": ???
"MY_CONTACTS_OVERFLOW_COUNT": ???
Bad requests:
"Request contains an invalid argument": something is wrong in the request, usually a Person object with some illegal info item
"Request contains a person.etag that is different than the current person.etag": An attempt to update a person that was recently updated on Google's side, need to fetch again
"Request person.etag is different than the current person.etag": same as above
"Requested entity was not found": An attempt to update a no-longer existing person
"Contact person resources are not found": same as above
"Contact group name is empty, expected to be non empty": An attempt to create/update a group with an empty name.
"Contact group name already exists": An attempt to create a group with the same name
"MY_CONTACTS_OVERFLOW_COUNT" happens when you try to insert contacts to a google account, but they already have the maximum number of contacts.
I am not 100% sure, but this limit seems to be ~20,000 for "normal"/"free" google accounts.
edit- The limit is 25,000, since 2011: https://workspaceupdates.googleblog.com/2011/05/need-more-contacts-in-gmail-contacts.html
I own a Magento CE 1.7 based website where we keep getting variations of the following error, usually after the daily morning site reindex:
"SQL ERROR: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'main_table.data' in 'field list'
SQL QUERY: SELECT DISTINCT main_table.data, main_table.lifetime, main_table.expire, main_table.priority, additional_table.*, IFNULL(al.value, main_table.frontend_label) AS store_label FROM eav_attribute AS main_table
INNER JOIN catalog_eav_attribute AS additional_table ON additional_table.attribute_id = main_table.attribute_id
LEFT JOIN eav_attribute_label AS al ON al.attribute_id = main_table.attribute_id AND al.store_id = 1 WHERE (main_table.entity_type_id (...)"
I have a website down detector set up so that I can know immediately when the site is unavailable. However it obviously doesn't detect whenever the site is unusable due to errors such as “SQL ERROR: SQLSTATE[42S22]”. That means that my team must be constantly manually (!!!) monitoring if the site is indeed working properly (by clicking on product and category links)!
Usually we surpass the error by just cleaning the cache or performing a new reindex.
My questions are the following:
1 - Is there a way of automatically perform a detection of this type of errors in Magento so that - if it happens - a cache cleaning (or a site reindex) is immediately run and an alert is sent to the webmaster?
2 – If such an error is detected, is there a way of it not be shown to the person accessing the site? That is, if the error is detected, is it possible to immediately display a message (“We’ll be back soon”) while the cache is being cleaned or the site reindexed?
I will be grateful for any help you can provide.
Thank you!
step 1:
request create inbound shipment plan api.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_CreateInboundShipmentPlan.html
response:
[
//usualy 1-5 plan has been reply,no any one plan contain full of my items.
//the plan 1
{
"ShipToAddress": {
... ignore address detail
},
"ShipmentId": "FBA15CQQTFFM",
"DestinationFulfillmentCenterId": "PHX3",
"LabelPrepType": "NO_LABEL",
"Items": [
//item list, it is alway not full of my provide items.
{}
]
},
//the plan2, and more plan
{},{},...
]
step 2:
choose max count items of plan for create inbound shipment.
i cant edit item in this step.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_CreateInboundShipment.html
step 3:
update inbound shipment plan for add all of item to this plan.
http://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_UpdateInboundShipment.html
request url: https://mws.amazonservices.com/FulfillmentInboundShipment/2010-10-01
request params:
SellerId=xxxxxxxxxxxxxxxxxx
AWSAccessKeyId=xxxxxxxxxxxxxxxxxxx
SignatureVersion=2
SignatureMethod=HmacSHA256
Version=2010-10-01
InboundShipmentHeader.ShipmentStatus=WORKING
ShipmentId=FBA15CR0QLLR
InboundShipmentHeader.ShipmentName=2018-05-16-AAA
InboundShipmentHeader.ShipFromAddress.Name=Wang%20Jingang
InboundShipmentHeader.ShipFromAddress.AddressLine1=396haozhiyihao
InboundShipmentHeader.ShipFromAddress.AddressLine2=
InboundShipmentHeader.ShipFromAddress.City=Guangzhou
InboundShipmentHeader.ShipFromAddress.DistrictOrCounty=
InboundShipmentHeader.ShipFromAddress.StateOrProvinceCode=Guangdong
InboundShipmentHeader.ShipFromAddress.CountryCode=CN
InboundShipmentHeader.ShipFromAddress.PostalCode=510080
InboundShipmentItems.member.1.SellerSKU=A71231811510311-
InboundShipmentItems.member.1.QuantityShipped=20
InboundShipmentItems.member.2.SellerSKU=A5W3E3112HE0
InboundShipmentItems.member.2.QuantityShipped=80
InboundShipmentItems.member.3.SellerSKU=A71231811540010-
InboundShipmentItems.member.3.QuantityShipped=20
InboundShipmentItems.member.4.SellerSKU=A71231811540011-
InboundShipmentItems.member.4.QuantityShipped=30
InboundShipmentItems.member.5.SellerSKU=A71231811515411-
InboundShipmentItems.member.5.QuantityShipped=20
InboundShipmentItems.member.6.SellerSKU=J8S109225HE90
InboundShipmentItems.member.6.QuantityShipped=10
InboundShipmentItems.member.7.SellerSKU=J8S109225HE92
InboundShipmentItems.member.7.QuantityShipped=33
InboundShipmentItems.member.8.SellerSKU=J8S109225HE93
InboundShipmentItems.member.8.QuantityShipped=10
InboundShipmentItems.member.9.SellerSKU=J8S109225ND90
InboundShipmentItems.member.9.QuantityShipped=8
InboundShipmentItems.member.10.SellerSKU=J8S109225ND91
InboundShipmentItems.member.10.QuantityShipped=12
InboundShipmentItems.member.11.SellerSKU=J8S109225ND92
InboundShipmentItems.member.11.QuantityShipped=17
InboundShipmentItems.member.12.SellerSKU=J8S109225ND93
InboundShipmentItems.member.12.QuantityShipped=14
InboundShipmentItems.member.13.SellerSKU=J8S109225ND94
InboundShipmentItems.member.13.QuantityShipped=5
InboundShipmentItems.member.14.SellerSKU=J8S109225QC90
InboundShipmentItems.member.14.QuantityShipped=10
InboundShipmentItems.member.15.SellerSKU=J8S109225QC91
InboundShipmentItems.member.15.QuantityShipped=5
InboundShipmentItems.member.16.SellerSKU=J8S109225QC92
InboundShipmentItems.member.16.QuantityShipped=9
InboundShipmentHeader.AreCasesRequired=false
Action=UpdateInboundShipment
Timestamp=2018-05-18T13%3A08%3A04%2B08%3A00
Signature=LCFu1NoX1QnENH1oCFEbwsXy1JVh7QNjpe2enGj258Q%3D
sometime success.
sometime fail, and tell me [skuType=MSKU, sku=..., reason=NOT_ELIGIBLE_FC_FOR_ITEM.]
do not change anything.
replicated 1-3.
sometime success.
sometime fail, and tell me [skuType=MSKU, sku=..., reason=NOT_ELIGIBLE_FC_FOR_ITEM.]
imcomprehensible it is, sku maybe not equal with last time. it is random, maybe one, mabe two.
can you tell me waht wrong?
HOW CAN I TO DO, MAKE ALL ITEMS IN ONE PLAN?
I got the sam error before, I found a ref.:
https://help.scanpower.com/support/solutions/articles/11000037578-what-does-the-not-eligible-fc-for-item-error-mean-
FYI, sure, I have a SKU, when creating inbound shipment, to old account, it's OK, but to new account, API will reponse the error you said.
Unfortunately, this error is coming directly from Amazon. There is a product in your shipment that is causing a conflict with the inbound shipping and/or the fulfillment center, but Amazon does not give us any indication as to the specific issue.
We have contacted Amazon and they suggest each seller experiencing this issue contact Seller Support for more information on the error. Please let them know that you are listing said item(s) via their MWS API and are receiving the following message: (insert the text of YOUR SPECIFIC ERROR MSG HERE what you see below is an example)
Invalid Items found - ShipmentId [FBA53HXYFX] MerchantCustomerId [A2WOJIKNACJWE4] InvalidItems[ (skuType=MSKU, sku=2016-11-30-B0006SGYS8-1099, reason=NOT_ELIGIBLE_FC_FOR_ITEM)]Shipment Id: FBA53HXYFXRequest Id: fb04a1f9-721f-4be3-a9c7-ba4063c13f69
I am working with the paypal express checkout API and am having issues.
I have a request like so:
METHOD=SetExpressCheckout
...
&L_PAYMENTREQUEST_0_NAME0=Individual%20Gross%20&%20Net
&L_PAYMENTREQUEST_0_AMT0=65.00
&L_PAYMENTREQUEST_0_QTY0=1
&PAYMENTREQUEST_0_AMT=70.26
&PAYMENTREQUEST_0_TAXAMT=5.26
&PAYMENTREQUEST_0_ITEMAMT=65.00
&PAYMENTREQUEST_0_PAYMENTACTION=Sale
&PAYMENTREQUEST_0_CURRENCYCODE=USD
I have reviewed this many times and see no error in the math, yet this is what paypal sends me.
TIMESTAMP : 2017-03-22T01:41:05Z
CORRELATION ID : e22e8009c7018
ACK : Failure
VERSION : 88.0
BUILD : 31129382
L_SEVERITYCODE0 : Error
Error Code : 10413
Transaction refused because of an invalid argument. See additional error messages for details.
The totals of the cart item amounts do not match order amounts.
I found that PayPal responded this way because I did not include L_PAYMENTREQUEST_0_NUMBER0 . After including that field, it was accepted. I must say that the error message sent to me lead to me to the wrong issue