HTTP trigger automatic deserialization from json loss of precision

[niphlod]

Describe the Bug

When trying to start a logicapp standard with an http trigger with this body

{
    "eventId": "92B82EA7-F64A-4A79-B8B9-019884278723",
    "data": {
        "ticks": 1754563833779314822
    }
}

the "triggerbody()" contains a slightly different number for "ticks"

{
    "eventId": "92B82EA7-F64A-4A79-B8B9-019884278723",
    "data": {
        "ticks": 1754563833779315000
    }
}

Plan Type

Standard

Steps to Reproduce the Bug or Issue

1. Create a standard logicapp with an http trigger
2. Send in the provided body
3. inspect the run and see the output from the trigger with an incorrect "ticks" property

Workflow JSON

Screenshots or Videos

No response

Additional context

No response