Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Here we will gather notes about current incidents and know issues.
Here you can check ongoing Atlassian Ecosystem issues which might affect apps, eg. app cannot be installed because of issues with Marketplace: https://status.atlassian.com/
Current App status: OPERATIONAL
Mar 4, 2025 We noticed some issues with job execution performance. We currently observe and working on the fix.
Mar 4, 2025 Issue with performance has been fixed and application is currently in operational state.
Jan 22, 2025 Application is not available
We are aware of the problem with accessing the Scheduler. We are currently analyzing and working on it to bring back application to operational state.
Jan 22, 2025 10:00 am CET - Issue has been fixed and application is in operational state.
May 27, 2024 Application is not available
We are aware of the problem with the Scheduler. We are currently analyzing and working on it to bring back application to operational state.
May 27, 2024 Issue has been fixed and application is in operational state.
Feb 26, 2024 Application is not available
We are aware of the problem with the Scheduler. We are currently analyzing and working on it to bring back application to operational state.
Feb 26, 2024 Issue has been fixed and application is in operational state. It may be required that SI with trigger date between Feb 25, 2024 10:00 am CET - Feb 26, 202411:00 am CET must be fixed using “Fix” button and then run failed Scheduled Issue manually.
Jul 26, 2023 Failed Scheduled Issues
We are aware of the problem with execution of some Scheduled Issue. We are currently working on it. You can easily rid of this issue by pressing the “Fix” button and then run failed Scheduled Issue manually.
Jul 26, 2023 Issue has been fixed. No more scheduled issues should fail. Existing failed SI can be fixed using “Fix” button and then run failed Scheduled Issue manually.
Jan 1, 2023 Migrations stuck at 0%
Jan 20, 2023 We are still investigating this, in the upcoming week we will release a special package with extra logs, if you are planning an upgrade, please wait until this is resolved.
Feb 5, 2021 Application maintenance
Database maintenance window has been planned for Feb 6 and Feb 7 9:00-9:30 GMT (there is a need to update database engine on AWS side). During this period application may be unavailable for several minutes. Tasks scheduled for this period will be executed with several minutes delay.
Dec 30, 2020 AWS deployment
“The Scheduler” pages sometimes did not load properly, the clock spinner had been loaded infinitely. This issue was caused by glitch while deploying app on AWS.
Nov 30, 2020 Required manual update
In some instances the app doesn’t load, it relates to changes in app. To solve this problem - navigate to manage apps section and update “The Scheduler” manually.
Nov 12, 2019 Permissions
We've noticed that Atlassian has introduced changes in Jira rest API on permission endpoint what may cause The Scheduler app being not accessible (scheduled jobs are still being executed on schedule). We are currently preparing fix,which should be released on 13 November. Moreover, the issue does not appear on every Jira Cloud instance.
Oct 21, 2019 User Interface of app not loading (tasks are being created on schedule) - Operational Again
Oct 7, 2019
We received few reports about dialogs not loading. We are still investigating this issue with Atlassian and seeing inconsistency in subsequent calls even without changes on our site. Moreover, the issue does not appear on every Jira Cloud instance.
We are testing solution to fix assignee picker, which is probably caused by Atlassian permission changes. We are still waiting for Atlassian response to confirm our supposition.
Oct 21, 2019 seems operational - without changes on our side. We don't receive any reports about related failures
Aug 19, 2019 - Duplicated issues
Recently (12.08), we had a failed release of version v2.6.0. After rollback to version v2.5.1 we were investigating our logs to see what went wrong in the first place. On day 19.08 we did some background tasks (to prevent future failed upgrades), which unexpected resulted in duplicate issue creation - for issues which were scheduled for executions that day.
We are very sorry for this incident, please remove those duplicated issues.