-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StelCore - B2C Exports - compliance check #1635
Comments
Log Report -- 30 August 2024 Report for Flow 1 -- on_search on_search/0/message/catalog/descriptor/images/0 must be object, not a string on_select on_select/0/message/order/fulfillments/0/https://github.com/ondc1org1category must be equal to one of the allowed values (Express Delivery,Standard Delivery,Immediate Delivery,Same Day Delivery,Next Day Delivery) on_init /on_init/0/message/order/provider/locations must be object not array confirm /confirm/0/message/order/billing/tax_id must be equal to constant (27AADCB2230M1ZT) on_confirm /on_confirm/0/message/order must have required property 'id' on_status /on_status/0/message/order must NOT have additional properties (brdName) /on_status/1/message/order must NOT have additional properties (brdName) /on_status/2/message/order must NOT have additional properties (brdName) /on_status/3/message/order must NOT have additional properties (brdName) /on_status/4/message/order must NOT have additional properties (brdName) /on_status/5/message/order must NOT have additional properties (brdName) @StelCoreM - As discussed and explained in the call earlier, kindly resolve the recurring issues. Reach out to me in case of any confusion. |
Log Report -- 06 September 2024 Flow 1 -- Schema Errors -- on_search /on_search/0/message/catalog/providers/0 must have required property 'creds' on_init /on_init/0/message/order/provider/locations must be object confirm /confirm/0/message/order/quote/price/value must be equal to constant (240) on_confirm /on_confirm/0/message/order/fulfillments/0/state/descriptor/code must be equal to one of the allowed values (Pending) on_status /on_status//message/order must have required property 'id' Context Errors -- on_select: context/timestamp difference between on_select and select should be within 30 seconds Message Errors -- on_search Flow 2 -- Incorrect Flow as per context/timestamps - (on_select,search,on_search,select,init,on_init,confirm,on_confirm,status,on_status) Schema Errors -- on_search /on_search/0/context/transaction_id Transaction ID should be same across the transaction: \3de5491e-0ead-472a-845c-0c5dfe89e51d on_select /on_select/0/context/location/city/code must be equal to constant (std:999) on_init /on_init/0/message/order/provider/locations must be object confirm /confirm/0/message/order/quote/price/value must be equal to constant (180.00) on_confirm /on_confirm/0/message/order/payments/0/@ondc1org1withholding_amount must be equal to constant (70.00) status /status/0/message/order_id must be equal to constant (3148-547359-1234) on_status /on_status/0/message/order must have required property 'id' Context Error -- on_init: context/timestamp difference between on_init and init should be within 5 seconds Message Error -- on_select Flow 5 -- Incorrect Flow as per context/timestamps - (search,on_search,on_select,select,init,on_init,confirm,on_confirm,status,on_status) Schema Error -- /on_search/0/message/catalog/providers/0 must have required property 'creds', Context Error -- select: Timestamp mismatch for /select Message Error -- on_search on_select select init on_init confirm on_confirm @StelCoreM - Kindly go through the above report for the issues in the logs. Additionally, share a demo video for the same post fixing. |
Log Report - 11 September 2024 Flow 1 -- Schema Issues - /on_search/0/message/catalog/providers/0/locations/0/city must be object /on_select/0/message/order/fulfillments/0 must have required property 'id' /on_init/0/message/order/provider/id must be equal to provider_id in on_search /confirm/0 context timestamp should be greater than created_at = updated_at /on_confirm/0/message/order/id must be equal to order id in confirm payload /status/0/message/order_id must be equal to order id in confirm payload /on_status/0/message/order/id must be equal to order id in confirm payload Message Issues - on_search select_0: on_select_0: on_init_0: confirm_0: on_confirm_0: Add ons in flow 2 -- Flow Error: Schema: /on_search/0/context/message_id Message ID should not be equal to transaction_id: \4f9c65ae-6e37-4adb-9647-ca94a9c3c823 /on_select/0/context/transaction_id Transaction ID should be same across the transaction: \1b9819b3-8e2f-421c-bff7-2a17ec65937b /on_init/0/message/order/quote/price/value must be equal on_select quote price Message: on_select 0 and on_select 1 have same payloads with out of stock messages on_select_1: select_0: Add on for flow 5 -- Schema Issues - /on_search/0/message/catalog/providers/0/items/0/quantity/available/count must be integer, /on_init/0/message/order/quote/price/value must be equal on_select quote/price/value /on_confirm/0/message/order must have the required property 'created_at' @StelCoreM - Kindly refer to the log report above. |
Flow 1 -- /on_search/0/message/catalog/providers/0/items/0/tags/2/list/2/value must be string /on_select/0/context/message_id Message ID for on_action API should be same as action API: \66a41100-fc8e-4b5d-8ac9-c99332b11cc7\ /init/0/context/transaction_id Transaction ID should be same across the transaction: \454a775e-931d-4770-a227-5af139c8572d\ /on_init/0/context/message_id Message ID for on_action API should be same as action API: \0794585a-c18e-4918-93dd-995d6d789bcd /on_confirm/0/context/message_id Message ID for on_action API should be same as action API: \0794585a-c18e-4918-93dd-995d6d789bcd /status/0/message/order_id must be equal to constant (3142-096887-3330) /on_status/*/message/order/id must be equal to constant (3149-710692-3421) Message: on_search_0: select_0: on_select_0: on_init_0: confirm_0: on_confirm_0: Flow 2 -- Flow Error: Schema: /on_select/0/context/transaction_id Transaction ID should be same across the transaction: \589b90e0-fa6e-455b-bfb6-968fbdf10590, /on_init/0/context/message_id Message ID for on_action API should be same as action API: \16bc5dbb-8d61-4a87-9a80-a557ff0d03a8, /confirm/0/message/order/quote/price/value must be equal to constant (250.00), /on_confirm/0/context/message_id Message ID for on_action API should be same as action API: \16bc5dbb-8d61-4a87-9a80-a557ff0d03a8, /on_status/0/message/order/fulfillments/0/state/descriptor/code must be equal to one of the allowed values (Domestic-Custom-Cleared,Pickup-Approved,Pending,Packed,Searching-for-Agent,Agent-assigned,Out-for-pickup,Pickup-failed,Pickup-rescheduled,Order-picked-up,In-transit,At-destination-hub,Out-for-delivery,Delivery-failed,Delivery-rescheduled,Order-delivered,RTO-Initiated,RTO-Delivered,RTO-Disposed,Cancelled), Message: on_select_1: on_search_0: select_0: on_init_0: confirm_0: on_confirm_0: |
Flow 1 & 5 -- Schema issue - on_init_0: FLow 2 -- Flow Error - Schema Error - /on_init/0/message/order/provider must have required property 'locations' /on_confirm/0/message/order/quote must pass \isQuoteMatching\ keyword validation Message Error - on_select (For items not in stock) Note --
|
Hi @StelCoreM Seems like a great improvement in the logs. Below are few more errors from Flow 2. Kindly share the select call logs for the item out of stock payload as well (for the message ID check). Log report for Flow 2 -- Message: |
Buyer and Seller Cancellation Flow Issues -- /on_confirm/0/message/order/cancellation_terms/2/fulfillment_state/descriptor/code must be equal to one of the allowed values - Domestic-Custom-Cleared For all the flows, kindly change the value of settlement type / payment type to OPGSP. |
Flow Issues -- Buyer Cancellation - Seller Cancellation - Flow 2 - For all the flows, kindly change the value of settlement type / payment type to OPGSP. |
Seller Cancellation — Buyer Cancellation — Changes pending from RTGS —> OPGSP |
How is the total calculation for the quote break in buyer cancellation wrong (because 80 - 10 != 0) but correct for the seller cancellation, when both are running on the same API's code? |
Hi Team,
There must be a mixup while creating the logs, sorry about that we'll make
sure this won't happen again.
Regards,
Sharmad Joshi
…On Mon, Oct 21, 2024 at 5:23 PM Sonali Shakya ***@***.***> wrote:
@StelCoreM <https://github.com/StelCoreM>
How is the total calculation for the quote break in buyer cancellation
wrong (because 80 - 10 != 0) but correct for the seller cancellation, when
both are running on the same API's code?
—
Reply to this email directly, view it on GitHub
<#1635 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKDY2R7T5ZZ2Q47REV3PKP3Z4TTNJAVCNFSM6AAAAABMLOCOA6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGQ2TQMRXGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
StelCore Management Services Private Limited
This e-mail message may
contain confidential and/or privileged information. If you are not an
addressee or otherwise authorized to receive this message, you should not
use, copy, disclose or take any action based on this e-mail or any
information contained in the message. If you have received this material in
error, please advise the sender immediately by reply e-mail and delete this
message. Thank you.
|
/on_search:
|
Flow 1
/on_select
/confirm
/on_status
Flow 2
/on_select
/on_init
Flow 5
/init
Buyer Cancel
/on_confirm
/cancel
Seller Cancel/on_cancel
@StelCoreM Please remove older files to avoid confusion. Let us know if there are any concerns, we can have a call in that case. |
StelCore (B2C Export)
All Flows --
Flow error -->
Incorrect Flow as per context/timestamps - Timestamps cannot be same and should be in the following order
Schema error -->
/on_search
std:999
./on_select
std:999
./init
std:999
./on_init
1org1provider_name must be equal to constant (Loadshare)std:999
./on_confirm
std:999
./status
std:999
./on_status
std:999
.Flow 2 --
/on_select
Flow 5 --
/on_select
/on_init
Cancellation logs need to be provided
@StelCoreM
The text was updated successfully, but these errors were encountered: