Skip to main content
Solved

Dynamic Block Date Not Displayed Correctly in Smart Delay

  • October 10, 2024
  • 2 replies
  • 32 views

elciospy

Hello,

I'm experiencing an issue with a dynamic block that returns a valid response but isn't working as expected in the flow.

I have a dynamic block that, in the test, delivers the following response:

```json
{"version":"v2","content":{"type":"instagram","actions":[{"action":"set_field_value","field_name":"LIVE_DATA_HORA","value":"2024-10-09T20:00:00.000Z"}],"quick_replies":[]}}
```

When I print this `LIVE_DATA_HORA` variable into a custom variable, it displays on Instagram as `2024-10-09T17:00:00-0300`.

The issue starts here because I want to use this variable in a **Smart Delay** as a dynamic date, but the delay is not respecting the date I'm getting from the server.

I would like to understand why this time difference is happening and how I can make sure the configured date and time are correctly used in the **Smart Delays**.

Here is the flow for your analysis:

- Shared: [link to the shared flow](https://manychat.com/flowPlayerPage?share_hash=806387719412447_c40cc58dda227fcbb2df99fa539152acfea27487)

Thank you for your attention, and I look forward to your guidance.

Best answer by Gustavo Boregio

2024-10-09T20:00:00.000Z is 20:00 UTC

2024-10-09T17:00:00-0300 is 17:00 GMT-3 (or 20:00 UTC)

The variable is set correctly, the only difference is how it’s being displayed.

@elciospy what’s the behavior that you want?

The proper datetime format accepted by Manychat (according to the docs) is:

2018-07-02T00:00:00+00:00

 

So, if you want the time to be set to 20:00 GMT-3, your server should reply with:

2024-10-09T20:00:00-0300

 

Does this make sense?

 

View original

Gustavo Boregio
Forum|alt.badge.img+6

2024-10-09T20:00:00.000Z is 20:00 UTC

2024-10-09T17:00:00-0300 is 17:00 GMT-3 (or 20:00 UTC)

The variable is set correctly, the only difference is how it’s being displayed.

@elciospy what’s the behavior that you want?

The proper datetime format accepted by Manychat (according to the docs) is:

2018-07-02T00:00:00+00:00

 

So, if you want the time to be set to 20:00 GMT-3, your server should reply with:

2024-10-09T20:00:00-0300

 

Does this make sense?

 


elciospy
  • Up-and-Comer
  • October 11, 2024

Hi Gustavo,

Thanks to your guidance, I was able to resolve the issue, and the automation is now working perfectly. I really appreciate your help!

Best regards!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings