Brokerage charges are not being credited after 1st july

Why brokerage charges are not being credited from 1st July when actual date is 31st August? My client id is 68ACEW

Why no one is replying to this?

I am getting CNs as earlier.

Why still no reply to this?

When should I expect reply?

i am also facing similar issue, when contacted CC they suggested to post it on community forum.

@Jagdish_j_ptl, your message has been forwarded to the back office team. We will provide a response soon. Thank you for your patience and understanding.

Can you share your user id for further investigation

508117

been told that backend team is looking to issue since last 7 days

508117,

till june end i got reversal (brokerage+gst), from july either im receiving partial reversal or nil

Apologies for the delay. We are currently investigating the issue with the concerned team regarding the mentioned UCC, as the flow is functioning correctly for others. We will get back to you as soon as possible.

Thank you for your patience and understanding.

Its 9 days and still you are checking?

@Jagdish_j_ptl @Vamshi_Krishna, Thank you for bringing this to our attention. We have investigated and resolved the issue. It should work fine starting tomorrow. This issue affected only a few selected users, so it took some time to identify. We will observe this tomorrow.

We will collect those orders and update the ledger as soon as possible for past transactions that were not reverted. We apologize for the inconvenience.

Note: The issue occurred due to a long tag string passed during order placement. We suggest using shorter tags when placing orders. We will implement a character limit on tags in a future release, so we recommend using shorter tag strings.

Thanks but If you limit tag limit then it will disturb our script as it is encrypted string which was working fine earlier but I don’t know why it stopped from July.

We need to store information for audit purposes, but such a large string constrains the database and increases storage size. People typically use shorter tags, which work perfectly.

I suggest using encryption to generate a shorter string.

I am already using encryption but encrypted string is large itself. And today is there any issue in nifty’s websocket ticks? sometime stopped receiving ticks.