Periodically and once

[manumanoj]

Hi

In my incident table, I created a field called maintenance, so in that field, Added field values called periodically, once if i select periodically i can select repeated interval and and starting date and time

POV:- For this i have created scheduled job there added periodically and repeated interval is 5 min and starting date time random scheduled job will execute every 1 minute 

in incident table if i select category as Hardware application  and sub category as printer for this need maintenance for every 15 min(example) so every 15 min it need to create incident 

for this i have wrote script but getting difference in timing for ex:- in scheduled job repeated interval is 5 min and start date and time 01-03-2024 (this is in scheduled job) in maintenance start date and time 02-03-2024 and interval is 29 min for every 29 min it need to create incident here time lapsing 

please help me on if any one know detailed configuration

[Tony Chatfield1]

Hi, jobs\events on the platform are not processed in 'real time', and can be batch processed and\or queued, actual processing may also take time, as a result you will not necessarily get an exact coloration between a 29 minute schedule interval and a resulting record with a timestamped sys_created_on that is a 29 minute increment.
Can you share your business requirement\use case so that the community can better understand your issue?

[manumanoj]

I have created scoped application extended with cmdb_ci table name called items 

in items added fields called category and sub category in category Hardware and sub category printer and if user select this and user need maintenance for this 3 hours(its an repeated intervel) so every 3 hours need to create and incident

[Tony Chatfield1]

Hi, I suspect that the number of tasks created following this approach will be high (if not excessive) with a high admin overhead, and the creation of maintenance tasks as incidents is also likely to cause confusion to users. But if that's the requirement you have been given then all you can do is point out the issues that it is likely to cause.
As a 3 hourly maintenance task I cannot see any system processing delay causing any end of world moments, if the tasks created time stamp is + seconds (or minutes) out, and I would not consider a maintenance task a suitable driver for a custom high priority event queue. In a scoped app you can set record timestamps using disableAutoSysFields()

GlideQuery | ServiceNow Developers

But if you are running SLA\OLA against the task with retrospective start then you effectively penalize the fulfillers delivering the solution for any system delays.

Perhaps if you can explain your business requirement\use case it might be easier for the community to understand the intention of the solution.