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

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[niphlod]

this is still a valid report, the issue hasn't been fixed

[influential-eliot]

... Simone Bizzotto (@niphlod) ... I'm interested in this ... I'm certainly not trying to push (as I am not part of the LA GUI project, and do not work for MS) ... but ... if you have literally any more information (that you can supply, either obfuscated or recreated) I'd love to know about it.

Cannot have values changing without reason, y'know? ( that's my concern for my own integrations )

[niphlod]

If you build a simple workflow with an httprequest trigger, and you push in the example body

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

and maybe initialize a variable of type object with "triggerBody()" you'll see the discrepancies between the body you injected in the request and the resulting variable.

Feel free to ask for more details, but it's a pretty straightforward case to reproduce.

[influential-eliot]

Cheers, mate ... will do ... out of interest ... have you seen this over multiple instances yourself?

[niphlod]

I only tested it on standard logic apps and it's always there. I guess it has to do with Json.NET handling of bigintegers but I can only assume, not verify ^_^

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[niphlod]

AFAIK this has not been fixed yet

[github-actions]

This issue is stale because it has been open for 45 days with no activity.

[niphlod]

unfortunately, still valid ...