Rapid account: REcodeX

REcodeX / fluis.lacasse

Discussions

460
Title
Created at (Click to sort ascending)
A
3
We've checked and aside the names there are no outdated dates. We can't change the names appearing in the responses but if the data you receive are wrong or outdated, we can solve that. Thanks. Wed 2:58 15/5/24
A
3
We've checked and aside the names there are no outdated dates. We can't change the names appearing in the responses but if the data you receive are wrong or outdated, we can solve that. Thanks. Wed 2:58 15/5/24
A
6
Thank you for your patience and support. No, it's not likely to happen, it was our fault in updating our servers. The deploy failed and we didn't get the notification but everything is okay now. From now we will be extra careful with updates. We also count on your feedbacks if you find anything wrong. Thsnk you. Fri 12:10 10/5/24
A
6
Thank you for your patience and support. No, it's not likely to happen, it was our fault in updating our servers. The deploy failed and we didn't get the notification but everything is okay now. From now we will be extra careful with updates. We also count on your feedbacks if you find anything wrong. Thsnk you. Fri 12:10 10/5/24
A
1
Hello, We're sorry about this issue. The responses are back to normal. Thanks. Fri 12:41 10/5/24
A
1
Hi, Sorry for the late answer. You can use this formula: Current Match Time=(Current System Timestamp−Current Period Start Timestamp)+Time Elapsed at the Start of the Period This Time Elapsed at the Start of the period can be inferred via status.description. Thanks. Sun 2:02 5/5/24