Incorrect timestamp returned in `ticks_history` response.

[0xkihato]

When making a request to the ticks_history endpoint with a specific end parameter timestamp, the response returns the latest tick data with a different timestamp than expected. I am issuing a request from the api explorer using the details below.

{
  "ticks_history": "R_50",
  "adjust_start_time": 1,
  "count": 10,
  "end": "1640985202",
  "start": 1,
  "style": "ticks",
}

Note that the end parameter is a timestamp whose datetime format is (2022-1-1, 0:13:22 UTC). However I get a response with the latest tick data:

"history":{
  "prices":[
  0:252.6844
  1:252.7016
  2:252.7002
  3:252.6632
  4:252.6145
  5:252.6417
  6:252.6786
  7:252.7007
  8:252.6653
  9:252.662
]
  "times":[
  0:1722807384
  1:1722807386
  2:1722807388
  3:1722807390
  4:1722807392
  5:1722807394
  6:1722807396
  7:1722807398
  8:1722807400
  9:1722807402
  ]
}
  "msg_type":"history"
  "pip_size":4
  "req_id":7
}

• Last tick timestamp: 1722807402 (2024-08-05 00:36:42 UTC)

Expected behavior: The response should return tick data with timestamps up to the specified end parameter timestamp (2022-01-01 00:13:22 UTC).

Actual behavior: The response returns the latest tick data with a different timestamp (2024-08-05 00:36:42 UTC).

Question: What could be the cause of this discrepancy?

CC @JamesK254 @chylli-deriv @balakrishna-deriv