Hey everyone! I’m new to NocoBase and trying to create an automation/workflow for due dates. I want orders to move to the “Late Orders” category if the due date is on or before the current date.
I’ve attached some pictures for reference—any help in understanding this would be greatly appreciated!
What specific problem are you encountering?
If accuracy down to the minute and second isn’t needed, I suggest the timer executes once a day. Execute it daily, set filter conditions to only process the necessary orders, and change the status to overdue if the deadline is earlier than today.
Since we’re still getting familiar with NocoBase, I tried to set up an automation that would move orders to the “Late Orders” category—or update their status accordingly—when the due date matches the current date.
You can create a Schedule event workflow that runs once a day to check if the due date is equal to or earlier than today, and then update the data status by Update node.
Thanks again for the suggestion!
I tried setting up the Scheduled Event Workflow to automatically move orders to the “Late Orders” category when the due date is equal to or earlier than today. However, I couldn’t get it to work as expected — the workflow doesn’t seem to trigger or update the status.
In another attempt, I used a condition where due_date is before System Time, and while the workflow did run, it moved all pending orders to “Late Orders”, even those with due dates in the future — which obviously shouldn’t happen.
Since we’re still learning NocoBase, it would be really helpful if you could guide us step by step or provide a sample configuration. Right now, we’re manually moving late orders, which is quite time-consuming.
Your support would be greatly appreciated!
Please refer to:
Workflow: Move to late - NocoBase
There are two main problems with your configuration:
ID = The ID of the queried delayed data to the condition.The demo I provided is just the simplest implementation. You need to adjust it according to the actual situation. For example, if there are a large number of delayed data, reaching thousands, then you need to use loops to query and process them in batches.