Here we will gather notes about current incidents and know issues
Current status: OPERATIONAL
Application maintance
Database maintance 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.
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.
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.
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.
User Interface of app not loading (tasks are being created on schedule) - Operational Again
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.
seems operational - without changes on our side. We don't receive any reports about related failures https://ecosystem.atlassian.net/browse/ACJIRA-1992
accessing the app
choosing assignee
We received few reports about app not loading, we are still investigating if its related to https://developer.status.atlassian.com/incidents/14hsjc7ts71n, we are seeing inconsistency in access without changes on our site
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.
seems operational - without changes on our side. We don't receive any reports about related failures
- 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.