Skip to content

Fix: [AEA-0000] - Silent running database fix#1893

Merged
wildjames merged 4 commits intomainfrom
aea-0000-fix-silent-running-db
Jul 9, 2025
Merged

Fix: [AEA-0000] - Silent running database fix#1893
wildjames merged 4 commits intomainfrom
aea-0000-fix-silent-running-db

Conversation

@wildjames
Copy link
Copy Markdown
Contributor

Summary

  • Routine Change

Details

Kayal has found that when we are using silent running, the database is not updated correctly. This is an exploratory PR to see what's going on.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jul 8, 2025

This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket:

AEA-0000

@wildjames
Copy link
Copy Markdown
Contributor Author

It looks like I wasn't paying attention to my changes in #1827 and when I was going through adding requestID to the debug logs, I accidentally added it to the key of the database pull. This causes the processor to fall over.

@wildjames
Copy link
Copy Markdown
Contributor Author

Attached is evidence of silent running working again

Notify Processor silent running
Notify state DB says silent running
PSU call

@wildjames wildjames enabled auto-merge (squash) July 9, 2025 09:12
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jul 9, 2025

@wildjames wildjames merged commit d09ce6e into main Jul 9, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants