07-25-2016 03:35 AM - edited 03-01-2019 04:30 AM
Hi
The asynchronous task concept is core to the REST API and how APIC-EM functions.
The basic pattern is to take the taskId from a request response, and then use the task API to check task status.
I am presuming that the system does not keep tasks around forever though, as that would bloat the database.
If my assumption is correct, how long does a taskId remain valid for please?
If my assumption is incorrect, then please let me know that also.
Many thanks
Nathan
07-25-2016 02:50 PM
With the current implementation, the task id's are kept for forever and we don't purge it.
07-28-2016 07:59 AM
Thanks Yawming. Is there a feature request to change this behaviour, or create an API to purge requests?
Regards
Nathan
07-28-2016 08:10 AM
Most likely need to add an expiry timer to purge in the future releases. I don't see any API to delete task.
Thanks,
Yawming
07-28-2016 08:16 AM
Thanks. I would expect to see a set of APIs for task lifecycle management, such as being able to delete a given task, or tasks over a certain age.
I’d also expect tasks to have a default lifespan, and to be archived to off-line log files after deletion for audit purposes.
Regards
Nathan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide