Tray Workflow |
Message |
Solution Instance ID |
Reason |
Tray Link |
Customer (rank) |
Action items |
|---|---|---|---|---|---|---|
Zendesk List Tickets |
Forbidden. Check you have the appropriate permissions to access this resource. |
|
It looks like provided credentials when the Connector were set up is not actual anymore or their permissions were changed |
(39) |
545
incomplete
Contact the customer and ask to check the authentication. Re-login to Zendesk from the connector configuration.
26 Jan 2024 it’s still not fixed from customer side, cc: 546 incomplete reach CSM (Grace) 547 incomplete Reached Jovanny and Tia about the issue |
|
Zendesk List Tickets |
Forbidden. Check you have the appropriate permissions to access this resource. |
|
It looks like provided credentials when the Connector were set up is not actual anymore or their permissions were changed |
http://ellevest.com (180) |
548 incomplete Contact the customer and ask to check the authentication. Re-login to Zendesk from the connector configuration | |
StripeDisputeToSiftChargeback |
|
|
|
quadpay.com (13) |
549
incomplete
Can be a small improvement to the Stripe connector flow with retry logic. create a ticket
550
incomplete
communicate the problem with the customer/CSM → missing filed in metadata problem. Specifically, they configured
26 Jan 2024 it’s still not fixed from customer side. cc: 551 incomplete reiterated with Kellie about the issue |
|
Zendesk List Tickets |
Forbidden. Check you have the appropriate permissions to access this resource. |
|
It looks like provided credentials when the Connector were set up is not actual anymore or their permissions were changed |
552 incomplete Contact the customer and ask to check the authentication. Re-login to Zendesk from the connector configuration. . Why we can’t find the customer in the list? | ||
http://chargeback.com chargeback_ingestion |
API error |
|
Required field(s) not specified: $.$order_id, $.$transaction_id |
intermittent errors related to missing |
||
Adyen <> Sift Chargeback Connector |
Reference: $.steps.trigger.body.notificationItems[0].NotificationRequestItem in property: 'object' did not resolve to any value. |
|
Parse error. No NotificationRequestItem field in the response from Adyen. Sometimes connector was called by a GET requests with no body. We expect POST and body inside with data |
http://cabify.com (25) |
We can contact customer to verify is those requests were made by him and maybe it’s something in their code they can change. Or it can be some sort of health check from Adyen side… cc: From : looks like misuse of the connector. The eventCode |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
|
Rate limited by Zendesk edge protection |
554
incomplete
Can be a small improvement to the Zendesk connector flow with retry logic. create a ticket
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
StripeDisputeToSiftChargeback |
Failed to reference: |
|
This object cannot be accessed right now because another API request or Stripe process is currently accessing it. If you see this error intermittently, retry the request. If you see this error frequently and are making multiple concurrent requests to a single object, make your requests serially or at a lower rate. |
Action item already presented in the table by adding a retry block for Stripe connector |
||
StripeDisputeToSiftChargeback |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. (merchant_reference missed in metadata) |
555
incomplete
Contact customer to verify they properly set merchant_reference for our mapping.
There are still the big amount of request with empty |
||
StripeDisputeToSiftChargeback |
API error |
|
Missed required parameters. Wrong mapping or missed field in the metadata. (exchange_order_id missed in metadata) |
556 incomplete Contact customer to verify they properly set exchange_order_id for our mapping. | ||
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. (id missed in metadata) |
557 incomplete Contact customer to verify they properly set id for our mapping. | ||
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. (charge missed in metadata) |
558 incomplete Contact customer to verify they properly set charge for our mapping. | ||
http://chargeback.com chargeback_ingestion |
API error |
|
Old one. can be the same error for missed required fields |
– |
||
Zendesk List Tickets |
Looks like the API is having issues. Please check the service status of the API provider. |
|
Old issue, not able to find in history. The last state for this solutions instance is Forbidden 403. |
new.bitso.com (39) |
Already have an action item above. |
|
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Some of the dispute events miss |
relayrides.com (66) |
559 incomplete Contact customer to verify they properly set charge for our mapping. 560 incomplete Original issue is fixed, there is another one. reiterated with Hernan about the issue | |
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. |
production.care.com (139) |
very intermittent one, usually chargebacks ingested well |
|
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. |
Disabled connector 561 incomplete to check with the customer/CSM why they disabled the connector |
||
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
|
Missed required parameters. Wrong mapping or missed field in the metadata. |
No executions at all, thought the Connector is active |
||
Zendesk |
Forbidden. Check you have the appropriate permissions to access this resource. |
d4bc0c60-001f-49f6-a6d5-92ce8f2f9d35 |
|
new.scribd.com (53) |
562 incomplete Contact the customer and ask to check the authentication. Re-login to Zendesk from the connector configuration. | |
Braintree Chargebacks |
disputes are without identifiers in last 24 hours |
f9cf9155-acc3-40b8-bf94-2e50d08169e7 |
Missed required parameters. Wrong mapping or missed field in the metadata. |
API-743379a65b29-991f-3e52-aa55-d37673426c85System Jira 563 incomplete - to contact with Tom Fisher about issues related to API KEY. UPD: the account is not active anymore, so Tray instance should be disabled |
||
Braintree Chargebacks |
disputes are without identifiers in last 24 hours |
b9b3590b-2982-4c44-98e8-cb1baa390154 |
Missed required parameters. Wrong mapping or missed field in the metadata. |
API-743379a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Braintree Chargebacks |
disputes are without identifiers in last 24 hours |
aa4a368f-5ff1-4dcc-833f-8ab6a818ea3b |
Missed required parameters. Wrong mapping or missed field in the metadata. |
API-743379a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
|
|
|
Invalid API Key. Please check your credentials and try again. |
swyftfilings.com (? ) |
Need to change SIFT-API-KEY. We have few options here:
cc: , 564 incomplete from : disabling the connector since the customer looks to be churned already |
|
|
|
|
Staring 16/11 all runs started to fail: no matching public key |
http://netlify.com (154) |
565
incomplete
Contact the customer and ask re-authenticate and provide proper Public Key from Braintree.
26 Jan 2024 it’s still not fixed from customer side, cc: |
|
StripeDisputeToSiftChargeback |
|
|
They specified the field |
Indiegogo (93) |
566
incomplete
contact the customer and let them know that some of the disputes miss the field they specified in Stripe Connector Config under metadata structure
|
|
CheckoutDisputeEventsHandling |
"Forbidden. Check you have the appropriate permissions to access this resource." |
|
Looks like some problem with access to Checkout.com for this specific customer (when we call for dispute details). Get Dispute Details step fails with 403 Forbidden. |
fastspring.com (156) |
567 incomplete Get Dispute Details step fails with 403 Forbidden. Customer has to check Checkout authentication. 568 incomplete communicate the problem to the customer/CSM (Jesse) 569 incomplete : reiterated with Jesse since the problem is still there | |
BraintreeDisputeToSiftChargeback |
Delay value for seconds must be in: Range 1 to 600 |
|
Send Sift Chargeback step returns 400 Then Random Helpers step returns:
It causes Random Delay step to fail:
It happened 15 times for the last 5 months. |
sift.fanduel.com (8 ) |
570
incomplete
Random Helper must return values from 1.
API-750479a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
BraintreeDisputeToSiftChargeback |
POST Request returned non-200 and is not a rate limit |
f9cf9155-acc3-40b8-bf94-2e50d08169e7 |
Invalid API Key. Please check your credentials and try again. |
Need to change SIFT-API-KEY. 571 incomplete Communicate to the customer to re-set up (Remove/Add) the connector. |
||
StripeDisputeToSiftChargeback |
Required field(s) not specified: $.$order_id, $.$transaction_id |
514220e6-6dfd-4f37-8028-fe946b91016e |
There is no |
572
incomplete
contact the customer and let them know that some of the disputes miss the field they specified in Stripe Connector Config under metadata structure
- contacted with Nathaniel |
||
Onfido Connector |
Reference: $.steps.script-1.result.idv_response.tags[0] in property: 'variables[].value' did not resolve to any value. |
bd2c8865-0526-417d-b4e3-9362cc3bb002 |
There is empty |
Need to investigate a root cause of the issue. API-753379a65b29-991f-3e52-aa55-d37673426c85System Jira cc: , |
||
Jumio Connector |
Reference: $.steps.script-1.result.customerRequestBody in property: 'body.raw' did not resolve to any value. |
c2a962f9-a3bd-402d-a926-8ea036a11b69 |
It were failed runs for this connector, but I dont see the Instance with such ID. Maybe someone played around with new connector. |
|
- |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
ead9f186-5784-497a-9bd6-e03556199032 |
429 - Number of allowed API requests per minute exceeded |
Can be fixed with retry API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
a8b12d30-fa51-4fb1-a56c-d15197f2d0ff |
Missed required parameters. Wrong mapping or missed field in the metadata. |
Laybuy |
rare event |
|
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
87432b18-50e9-466e-b413-1d67ae88b604 |
Missed required parameters. Wrong mapping or missed field in the metadata. |
|
||
BraintreeDisputeToSiftChargeback |
no matching public key |
6b17b071-5fc2-4f35-a15e-004c2fd4f0b6 |
We had similar issue above ^. Need to ask customer to re-authenticate |
|
||
Zendesk List Tickets |
Forbidden. Check you have the appropriate permissions to access this resource. |
5d100c53-89ae-408f-b06d-c61d2a6a54dc |
|
atomtickets.com (74) |
573 incomplete contact with CSM | |
Zendesk List Tickets |
Forbidden. Check you have the appropriate permissions to access this resource. (link) |
472fafc5-2f7e-422f-8eee-448c3c257b6e |
It looks like provided credentials when the Connector were set up is not actual anymore or their permissions were changed |
v2.humblebundle.com (95) |
574 incomplete Contact the customer and ask to check the authentication. Re-login to Zendesk from the connector configuration. | |
Zendesk List Tickets |
Reference: $.errors.zendesk-2.response.body in property: 'body' did not resolve to any value. |
bd1b6b84-4a4d-4f7b-ac65-123f997df551 |
API call timeout. Looks like the API you're calling is having a wobble. Please try again later. |
uphold.com (9) |
Only 1 such case, can be handled using retry. Added this case into existing ticket API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Reference: $.errors.zendesk-2.response.body in property: 'body' did not resolve to any value. |
b24a04e0-9e2b-4eaf-ae41-cf95cfd26ad0 |
API call timeout. Looks like the API you're calling is having a wobble. Please try again later. |
redbubble.com (69) |
Only 1 such case, can be handled using retry. Added this case into existing ticket API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
http://chargeback.com chargeback_ingestion |
Reference: $.steps.trigger.body.dispute_profile.order_transactions in property: 'variables[].value' did not resolve to any value." - example |
d43e44f3-78eb-4d85-b839-823037933c73 |
No field |
Not all chargebacks are failing. Some chargebacks contain |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
2dc6319b-6ac9-4804-aab0-7734ec5358b7 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
2de4309d-97f9-4577-9104-504bcfe5bacc |
Rate limited by Zendesk edge protection |
http://tcgplayer.com (56) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
3439bb4d-47f1-466e-84b9-daee20fe45b0 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
55f8b2ad-b3e3-4406-9811-be64761207ce |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
6d91c425-71e9-49e8-a836-6716a9600030 |
Rate limited by Zendesk edge protection |
http://outdoorsy.co (175) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
86f722e6-e305-4684-863b-1092147c9c53 |
Rate limited by Zendesk edge protection |
http://careerplug.com (190) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
8ac73623-2c0c-40a3-830f-78647384c8e5 |
Rate limited by Zendesk edge protection |
http://pinterest.com (206) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
8b82ed8e-cc3b-4cef-b164-a07dac79b3b3 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
a5791b75-6be3-4ee0-820e-3a73e6af5604 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
aefeda04-60ca-465e-9fdc-3e9a174e6836 |
Rate limited by Zendesk edge protection |
http://stitchfix.com (34) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
af9e38cd-5952-4340-a0ef-5e0f4b7f370d |
Rate limited by Zendesk edge protection |
http://patreon.com (41) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
c36a1f10-ee11-4141-b0ef-2c57653ae749 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
d42dcf74-21c8-42f9-bdc1-eeacbe3f5396 |
Rate limited by Zendesk edge protection |
http://cabify.com (25) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
d4fa9936-10ef-452e-8459-55449514310f |
Rate limited by Zendesk edge protection |
http://paulaschoice.com (119) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
ed15f9cd-4b0d-49e8-8a65-93f527aa3518 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Stripe Periodic Alerting |
disputes are without identifiers in last 24 hours |
689b5e27-2e91-4e78-bf0d-f6b3272cdf95 |
Stripe Calls Failed for 689b5e27-2e91-4e78-bf0d-f6b3272cdf95 |
|
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
8ee063df-60ab-437b-86d1-f7b4022fe31b |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
a8a3e5cd-0b55-4821-81a7-ae0639ff353b |
Rate limited by Zendesk edge protection |
huckberry.com (102) |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
|
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
945cf12d-8ee9-4748-b84d-a00bec5cd69c |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
Zendesk List Tickets |
Too many requests have been made in the given timeframe. |
ab859e40-9609-4ad9-8488-09a8fd81afa0 |
Rate limited by Zendesk edge protection |
API-743279a65b29-991f-3e52-aa55-d37673426c85System Jira |
||
StripeDisputeToSiftChargeback |
Failed to reference: |
3e5aee4f-6dd3-4093-97ed-edeed4a9bc04 |
403 The provided key does not have the required permissions for this endpoint on account Having the 'rak_charge_read' permission would allow this request to continue. |
fr.nespresso.com (20) |
575 incomplete Contact customer to check api_key | |
BraintreeDisputeToSiftChargeback |
POST Request returned non-200 and is not a rate limit |
42c3d07b-fc90-4b56-8e54-a33d8cde5ea2 |
400 - Invalid API Key |
576 incomplete Contact customer to check api_key |