I have a few automations which stopped working out of the sudden. I've found out it's due to my "Lookup objects" not working correctly anymore. To troubleshoot, 'Ive done the following: - Created a new automation with Lookup Objects and ELSE IF statements. - Lookup objects tested with * "non-existing" filter, results in the log showing under task "Lookup objects" "No objects found" & log empty -- to be expected * "Existing filter" (tested in assets -- shows objects), results in the log do not show "no objects found" (-- to be expected), yet the log for {{lookupObjects}} is still empty AND the IF statement for "{{lookupObjects.size}} equals EMPTY" is triggered as well. I do not seem to find why my {{lookupObjects}} remains empty, this used to work as expected before (last valid try 04/05/2026 17h). Anyone have any idea?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - {{lookupObjects}} remain empty

Thomas Pollet

I have a few automations which stopped working out of the sudden.

I've found out it's due to my "Lookup objects" not working correctly anymore.

To troubleshoot, 'Ive done the following:

- Created a new automation with Lookup Objects and ELSE IF statements.

- Lookup objects tested with

"non-existing" filter, results in the log showing under task "Lookup objects" "No objects found" & log empty -- to be expected
"Existing filter" (tested in assets -- shows objects), results in the log do not show "no objects found" (-- to be expected), yet the log for {{lookupObjects}} is still empty AND the IF statement for "{{lookupObjects.size}} equals EMPTY" is triggered as well.

I do not seem to find why my {{lookupObjects}} remains empty, this used to work as expected before (last valid try 04/05/2026 17h).

Anyone have any idea?

Accepted answers

Sam Okell

Hi @Thomas Pollet

We've noticed the same behaviour this morning and I believe this to be an incident on Atlassian's side.

We've raised a support ticket, but would suggest that you do the same to raise the awareness and hopefully speed up any resolution.

Thanks,

Sam

Evgenii

Hi

Yes, it's Atlassian side problem.
You can track that incident:
https://jira-service-management.status.atlassian.com/incidents/5mlknfjbkddm

All comments

Sam Okell

Hi @Thomas Pollet

We've noticed the same behaviour this morning and I believe this to be an incident on Atlassian's side.

We've raised a support ticket, but would suggest that you do the same to raise the awareness and hopefully speed up any resolution.

Thanks,

Sam

Thomas Pollet

Hey Sam,

Thanks so much!

Will raise the same on our side then!

Julian Becher

We have the same problem.

Evgenii

Hi

Yes, it's Atlassian side problem.
You can track that incident:
https://jira-service-management.status.atlassian.com/incidents/5mlknfjbkddm

Sam Okell

Hi @Thomas Pollet

We've had confirmation from Atlassian that this was resolved on their side now, so hopefully you are seeing this work now!

Thanks,

Sam

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-cloud

automation

jira-service-management-cloud

jira-service-management

assets

cloud-automation