Hello @Rafael Fernandes
What is your level of admin access for this environment? Are you only an administrator for individual Projects (Spaces)? Are you a Jira Product Administrator? Are you an Organization Administrator?
Are you using a paid Jira subscription?
If you are on a paid subscription and you are a Jira Product Admin or Organization Admin, and if this is a recurring problem across multiple automation rules I recommend that you contact Atlassian Technical Support directly to get assistance. They can examine the database and other backend elements that we cannot see.
https://support.atlassian.com/contact/#/
Only Jira Product Admins and Organization Admins can create support cases. If you don't have that level of access then you should report this problem to your Jira administrators and ask them to engage Atlassian Technical Support.
Is the problem sporadic for any given rule?
Have you found any solution that works, even temporarily?
Has it occurred with rules you've created recently? With rules that have existed for a long time?
Is there any common element to the rules where this occurs versus rules where it does not occur? Rule scope, Actor, Owner, types of Triggers, ...?t.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.