JS custom params no longer using param name

[David]

This appears to have only occured (consistently) since around 11am (GMT) today, but custom params have suddenly changed name to the name of the variable being provided instead of the name of the defined custom param. This is causing some merry hell with my custom JS code. Screenshot attached showing example.

[TimePaste.com]

This is a big problem. It’s caused my and my client’s scenarios to go haywire today.

[David]

@Raian if this is system-wide, it’s indeed a serious P1 issue, and I’m a bit surprised something so serious got past QA

[Oleg]

It should be fixed now, sorry for inconvenience

[David]

@Oleg thanks, but I think a serious issue like this needs further explanation as to how it happened, how it was resolved and how it will be prevented in future as this is fundamental functionality that can never afford to fail the way it did.

[Oleg]

Absolutely, we will provide more details next week

[Grav]

@David Thank you for sharing your thoughts and taking the time to write to us. I understand how serious this issue was and how it might have affected your experience. Let me address your questions as openly and clearly as possible.

1. How it happened: After conducting an internal investigation, we found that the issue occurred due to an oversight during testing. Unfortunately, the particular scenario that caused this problem wasn’t accounted for in our current processes.

2. How we fixed it: As soon as we learned about the issue, our team quickly identified the root cause and implemented a fix. The solution went through additional checks to ensure everything works as expected. The update has already been deployed, and the problem has been resolved.

3. How we’ll prevent this in the future: We’ve learned a lot from this situation and have already started making changes:

   • Expanding our test coverage to include similar scenarios.
   • Improving our review and release processes.
   • Conducting a thorough analysis to identify and fix any other weak spots.

We understand that such incidents can shake trust, and we deeply regret what happened. It’s important to us that you can rely on our product at all times. We’re doing everything possible to make sure this doesn’t happen again.

Thank you for bringing this to our attention. If you have any further questions or feedback, please don’t hesitate to reach out. We’re always open to dialogue.

[David]

Thanks @Grav, the transparency from the post mortem is helpful and also aids in trust, so I very much appreciate the response.