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; } } }

When: Object Created trigger doesn't trigger

Rune Rasmussen

Hello

I am attempting to create a global automation that triggers when an Assets Object is created.

Currently the trigger doesn't trigger for me.

This is my very simple automation:
Screenshot 2024-10-16 131918.png

I have also allowed this automation to be triggered by actions from other automations, but the automation doesn't trigger when other automations create Objects in the System List schema or when I do it manually.

What could I be missing?

Response from Atlassian support, 25-10-2024.

Sorry about the delayed automation execution for Assets Object Created. We are aware that for a few sites, there is a delay in automation rule execution and our devs are actively trying to fix it.

At the moment, we don't have any workaround for you but we are trying to fix the performance issue internally.

Bug report:

https://jira.atlassian.com/browse/JSDCLOUD-15236

Accepted answers

Rune Rasmussen

For some reason it took my automation almost 20 minutes to trigger.
Weird!

All comments

Jack Brickey

Hi @Rune Rasmussen , theory - the object category doesn't match the created object. I see you have selected System list, does it match that which you created?

Rune Rasmussen

The Object Type I am creating is "System" in the "System List" Object Schema.

I can only select Schemas in the automation trigger, but not Object Types.

Marc -Devoteam-

HI @Rune Rasmussen

From my recollection, this trigger will only launch if you have another automation rule triggering this rule and in that automation rule and object is created within Assets.

Rune Rasmussen

For some reason it took my automation almost 20 minutes to trigger.
Weird!

Rune Rasmussen

Seems that it's just very slow.
Looks to take 20 minutes before the automation triggers.

Rune Rasmussen

That would be very strange, but also not something I would be surprised if Atlassian had decided and then just not documented (anywhere that I can find at least).

But right now it just seems to be very slow. Around 20 minutes from my test to the automation triggering.

Jack Brickey

Very odd. I would be interested in the cause so you might ask Atlassian support.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud

automation

jira-service-management-cloud

jira-service-management

assets

global-automation