Budibase / budibase

Low code platform for building business apps and workflows in minutes. Supports PostgreSQL, MySQL, MariaDB, MSSQL, MongoDB, Rest API, Docker, K8s, and more 🚀
https://budibase.com
Other
22.62k stars 1.56k forks source link

Automation cron server timestamp isn't working correctly, it shows the time its added to the queue rather than at runtime #14671

Open ConorWebb96 opened 1 month ago

ConorWebb96 commented 1 month ago

Checklist

Hosting

Describe the bug When using the timestamp provided in cron automation, it didn't show the correct timestamp. Instead, it used the date + time when the automation was added to the queue.

To Reproduce Steps to reproduce the behavior:

  1. Add a cron automation
  2. Configure the cron expression to run every minute
  3. Check the timestamp after running
  4. Notice the timestamp in automation doesn't match the one in history. Will be off by however many minutes it was since publishing

Expected behavior The timestamp should be when the automation ran rather than the app's published time of being added to the automation queue. The screenshots below show this. The timestamp in the below automation should be a few days old rather than 21 days old.

Screenshots

Screenshot 2024-10-01 at 08 19 38 Screenshot 2024-10-01 at 08 20 04
linear[bot] commented 1 month ago

BUDI-8683 Automation cron server timestamp isn't working correctly, it shows the time its added to the queue rather than at runtime

yueum commented 2 weeks ago

Same here.