We are experiencing changes made to asset objects not reflecting in the activity logs and automations that should trigger on object updates not being processed.
Anyone else experiencing this in JSM cloud?
Is this a relatively new issue for you, or have you always noticed it? I've noticed before that after doing an Asset import, the activity log isn't up to date with something that I've just imported, and that searching for a value I know has changed doesn't work immediately, but eventually, it updates (background indexing update maybe?).
I'll keep a closer eye on the next few updates I do to see if anything jumps out at me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.