​@Craft Travels you probably have something else somewhere that’s causing the issue…

But to be sure, try a flow like this:

https://app.manychat.com/flowPlayerPage?share_hash=639235_0dbf5220d9f48ca08712b9708891b0d811ce6dc5

You should get something like this:

If the time difference isn’t the time you set, open a ticket with support ;)

In this test you can see it’s exactly 10 seconds, as set on the Smart Delay.

Thanks ​@Gustavo Boregio I'll get back to you.

Gustavo, I could verify that all timestamps that I used throughtou the automation returned me 10 secs most of the time (I used instagram messages instead of telegram's).

Interestingly i noticed that i was receiving “late message blocks” of inumerous timestamps that went off 15, 20 or even 30 seconds ago.

Also, if I try to use long loops with more than 10 iterations I realized that Manychat halts the automation without warning.

Just to let you know, I'm using Manychat together with ChatGPT's API through FTP Calls.

​@Craft Travels yes, there’s loop prevention in Manychat, more than 30 steps without a pause will cause the automation to stop without warning.

As for the delay times, it could be related to the loop prevention also. If it’s a problem, you’ll need to contact support (or optimize your automation).

I have the same problem. Every time my automation enters the smart delay, the execution time is not respected. It starts at 5 minutes (that's how I have it configured), and as time progresses, the smart delay runs at 6, 7, 8, and even 15 minutes, even though the indication is 5 minutes.

It only returns to 5 minutes if I unsign the contact and sign it again.

Hey ​@Jose Ortega Fig do the test I mention above.
This is the fail-safe way I have to find issues.
If it’s indeed working wrong, you’ll have irrefutable proof to show support - and it will also help them find any issues because they’ll be able to reproduce the scenario.