bad_msg_notification when using the same account simultaneously on multiple instances

[ip]

I'm trying to get my development server working while the production is running. I'm using different tokens. On the development I'm getting these responses for any request:

{"id": 0, "message": {"_cons": "bad_msg_notification", "bad_msg_id": 6532164331258096284, "bad_msg_seqno": 3, "error_code": 17}}

Telegram docs suggest that error_code == 17 has something to do with msg_ids. They tell that "the client time has to be synchronized, and the message re-sent with the correct msg_id". Anyone knows what does it mean?

@milch @lattenwald

[nikat]

Hi. Try to check if the timezone at the development server is correct.

[ip]

Should it match one at the production?