Skip to content

Commit f2495d9

Browse files
Peter JohnsonPeter Johnson
authored andcommitted
Minor corrections
1 parent 72202dc commit f2495d9

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/releases/status.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,21 +22,21 @@ Some evaluation functions returned errors.
2222

2323
### Timeline (UK / GMT)
2424

25-
2025/11/18 21:18 GMT: some but not all feedback functions failed. Investigation initiated and message on home page
26-
2025/11/18 21:39 GMT: updated to users that the cause was identified.
25+
The application was fully available during this time period.
26+
27+
2025/11/18 21:18 GMT: some but not all evaluation functions (external microservices) failed. Investigation initiated and message added on home page
28+
2025/11/18 21:39 GMT: home page updated to users that the cause was identified.
2729
2025/11/18 21:45 GMT: issue resolved. Home page updated.
2830

2931
### Analysis
3032

31-
Some of our evaluation functions still use an old version of our baselayer, which calls GitHub to retrieve a schema. GitHub git services were down (https://www.githubstatus.com/incidents/5q7nmlxz30sk), which meant that our functions could not validate their schemas and therefore failed.
32-
33-
The same issue meant that we could not push updates to code during the incident, due code being deployed via GitHub. GitHub had announced they were resolving the issue, and when it was resolved our services returned to normal.
33+
Some of our evaluation functions still use an old version of our baselayer, which calls GitHub to retrieve a schema and validate inputs. GitHub git services were down (https://www.githubstatus.com/incidents/5q7nmlxz30sk), which meant that those of our functions that call GitHub could not validate their schemas and therefore failed. Other evaluation functions had previously been updated to remove the need to call GitHub and were therefore not affected by the issue.
3434

35-
The solution in this case is to upgrade all of our evaluation functions to a newer version of the baselayer, which has schemas bundled and does not rely on external services.
35+
The same root cuase meant that we could not push updates to code during the incident, due code being deployed via GitHub. GitHub had announced they were resolving the issue, and when it was resolved our services returned to normal.
3636

3737
### Recommended action
3838

39-
Update all evaluation function baselayers.
39+
Update all evaluation function baselayers to remove dependency on external calls when validating.
4040

4141
N=1, effect = 2, duration = 0.5. Severity = 1 (LOW)
4242

0 commit comments

Comments
 (0)