Direct Mysql Insert statement results with UTC_TIMESTAMP differs from same wappler API Insert statement

Hi Community,
I’m new to Wappler, not to programming, so far, love the ease of use with Wappler and how it has expedited my code implementation! Thank you Wappler Team!

Here is the discrepancy I’ve encountered when using specifically the UTC_TIMESTAMP function in an insert/update statement, when I run the following statement directly in MySQL I get the following result
INSERT INTO dummyTable (id, user_id, disposal_date) VALUES (1234, 1, UTC_TIMESTAMP) --> Disposal Date Result --> 2022-01-21 23:33:19

When I run the same Statement via the Wappler API I get a different result, which I believe the Wappler backend interprets the UTC_TIMESTAMP as a NOW() function, opposed to UTC function.
INSERT INTO dummyTable (id, user_id, disposal_date) VALUES (:P1 /* {{$_POST.id}} /, :P2 / {{identity}} /, :P3 / {{UTC_TIMESTAMP}} */)
Disposal Date Result --> 2022-01-21 18:33:36

My question is how can I write a consistent statement with the UTC_TIMESTAMP function in Wappler to expect the same results as I input into MySQL?

Thank you