Amit,
Can you explain the advantage of using the external-facing ServiceNow http API to query the task table, versus using GlideRecord? It seems to me GlideRecord is simpler and likely faster in this context, and doesn't require setting up credentials.
I can see the advantage of putting a schedule on the flow: it means you do not have to check if an incident has already been created. But if the incident can be identified somehow, such as through its short description, then the process can respond to the creation of a task by checking if an incident has been created recently (I described this above). Because the process runs each time a task is inserted, it will always know how many have been set up in the last hour. In this scenario the schedule is not needed, and only slows the process down.
