[BUDI-7447] Finish and test automation for cron trigger timestamp binding is incorrect type (string instead of number)

[melohagan]

Checklist

• I have searched budibase discussions and github issues to check if my issue already exists

Hosting

• Self
  • Method: docker compose
  • Budibase Version: 2.9.36

Describe the bug
I initially thought the filtering was broken, but I believe it's specifically that the test input for the timestamp is being ignored, and the cron job is using the actual current timestamp.

To Reproduce
Steps to reproduce the behavior:

1. Add an automation with cron trigger: 0 * * * *
2. Add a step: Query Rows for the 'Employees' table
3. Define filters: Start Date More than or equal to Binding:

return new Date($("trigger.timestamp") - (2 * 60 * 60 * 1000))

1. Finish and test automation
2. Enter a timestamp of a past date that would return values (e.g. 2014)
3. See that no values are returned.
4. Go to the Employees table, and set some of the start dates into the future (e.g. 2024)
5. Test the automation and see that those rows will be returned

Expected behavior
When running an automation test, the input timestamp should be used and not the current timestamp.

Screenshots

This should return all rows

But only the checked rows are returned by the query rows

Additional context
As this is filtering on the timestamp number type field, it may be related to this bug: #11418

_{From SyncLinear.com | BUDI-7447}

[melohagan]

Re-opening as this is still a problem. It's not specific to filtering, the issue is that when testing the timestamp is of type string and must be cast to a number, however in production it correctly has the number type.

The fix would be to ensure timestamp is of type number when testing.

const currentDate = new Date($("trigger.timestamp"));

This will work in production, but not in test

const currentDate = new Date(Number($("trigger.timestamp")));

This will work in both test and production, but shouldn't be necessary

---

[melohagan]

To add to this one, it does appear to not work in production either.

For example this works:

const triggerTimestamp = $("trigger.timestamp")
const currentDate = new Date(1700211176994);

but this does not:

const triggerTimestamp = $("trigger.timestamp")
const currentDate = new Date(Number(triggerTimestamp));