Can't find anything in the documentation about it. Does it clear the cache of the Atom? What will happen if I'm running a process meanwhile?
Apologies, just saw this. This option basically just tells the platform to "forget" the Atom's status (from the platform's perspective) and get the current status the next time the Atom pings home. It is only intended to be used to help with troubleshooting if the status appears to be "stuck" from the platform's perspective.
To be clear it does not affect the Atom's actual status or executing processes in any way.
Thanks for the reply. There was nothing in the documentation about it that's why I had to ask.
Do you know if there's a way to clear the cache of the atom?
Thanks George. I've submitted a note internally for that.
What do you mean by "cache of the atom" (document cache, JVM heap memory, component config, something else)? This is not a common request so can I ask what's prompting the question?
Sorry my question was too broad. I'm asking regarding document cache. We had a large migration of documents and we were wondering if it's possible to delete the cache from the server after we were done, instead of waiting the X amount of days to be automatically deleted.
Ok it sounds like you're talking about the document data execution artifacts that are persisted on the Atom (vs. Document Cache components), is that correct?
If so, the Atom purge setting is your only option. As part of a one-time migration, I would recommend temporarily setting this to 1 day or even "purge immediately" while you do the migration. Remember the purge setting is for the entire Atom, not per-process, so you probably wouldn't what to have that aggressive a purge setting for production because you'll likely need those documents for troubleshooting/reprocessing.
Indeed you are correct. Thank you very much for the help!
Retrieving data ...