Allow for a "recurrence" to Tasks. Something like "every 6 months". This would allow for recurring tasks like preventative maintenance or task that needs to be done more than once.
@JonathanPollack thanks for submitting this idea. I had the same thought when tasks were first released too and after discussing this with some Esri staff at the 2026 Esri UC, it was suggested I submit an idea but you @JonathanPollack beat me to it 👌.
@ChrisDunn1 it is a creative idea to use a calculation to "reopen" a completed task at a set interval. However, many customers like likely @JonathanPollack and I need to preserve history in the data. Most scenarios users would utilize tasks would be as a child related layer (many to one) to a parent layer representing features (assets or something) that need the tasks executed upon. It certainly is possible via ArcGIS Notebooks, ArcGIS Data Pipelines, ArcGIS Workflow Manager, Microsoft Power Automate, and much more to create reoccurring tasks at a given frequency to emulate this. This essentially creates the ability for tasks to be leveled up closer to a full suited work order management system and given how many scenarios for many Esri customers this would be useful, it would be strongly recommended. Not because technical users like myself can't recreate scheduled tasks via the tools mentioned, but this lowers the bar for all customers to create reoccurring tasks within the task software itself and makes it more accessible to less technical users. It is an extremely common pattern for a system to offer reoccurring tasks, so it has proven value worth investing in. I would be happy to discuss more and setup a call if interested.
For some additional context, my organization would love to bring more of our work order management to the ArcGIS platform and tasks opened my team's eyes to doing so. We are not the only team either contemplating this, having talked to a dozen other teams that are ArcGIS users who have an existing asset / work order management system they are not ecstatic about for one or more reasons (like my organization) or no current work order management system. This is an opportunity for Esri...
Hi @RobBlackbourn ,
How you handle recurring tasks will partially be determined by how you utilize your task layer.
The simplest version would be to have a single task feature representing the task that needs to happen on a specific interval (such as a monthly inspection) and use an automatic calculated expression on your "Finish" feature action that will add the desired time interval to the due date field. The arcade would look something like this:
var current_due_date = $originalFeature.esritask_duedate return DateAdd(current_due_date, 1, 'month')
There are a few things to consider in this scenario though. Do you need to keep a history of the tasks being performed? Should the status value become something other than "Completed" when you press the Finish button?
If you want to use a separate task feature for each inspection, you may wan to look at using a webhook with something like Power Automate to duplicate and re-assign new tasks when the old ones are closed out. You could also do this with a manual process if you have a dispatching map that only shows recently closed tasks and you can create new ones based off of those.
I'm happy to dig into your workflow a bit and discuss this further, feel free to reach out to us at arcgisfieldmaps@esri.com with some more details about your needs for recurring tasks and we can always set up a call.
Chris
Hi @ChrisDunn1
I was reading above and was wondering if you had any thoughts on setting up different frequency tasks. We are currently using Field Map Tasks to assign exceptional tasks but I would like to set up so I can also cover reoccurring tasks (weekly, monthly, 6 monthly etc.). Any suggestions would be much appreciated.
Cheers
Rob
Hi @JonathanPollack ,
It is possible to set this up now, the best way to do it will depend on your Tasks configuration.
If you are using the due date field to drive work, the simplest way would be to add an automatic calculation to your "Completed" or similar task action that updates the due date by whatever interval you need when the task is completed.
If you can share more details about how you're implemented Tasks I'd be happy to offer some suggestions.
Sign in to post, follow content, and more. New here? Register for free.
