job-update-credit-limit
Nightly console job that recalculates credit-limit balances for business customers with activity that day, acting as a fallback for when automatic balance updates are incorrect.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | TC.MaintainanceTools.SimpleJobs 4, TC.ConnectionBroker 1.13 |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-06-27 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Payments and finance (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 1 release pipeline(s): \finance\jobs\job-update-credit-limit CI |
| Integration | wcf |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Speaks WCF (client)
Detaches when its WCF surface gains a modern interface or its WCF calls move to one.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
Ready with guardrailsClose: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
job-update-credit-limit
Purpose
Nightly fallback job that finds business customers with activity during the day (via a recently-changed customer source, with an alternative all-ids-from-backoffice source) and recalculates their balances/credit limits through the Phenix booking service, logging differences it corrects.
Tech stack
- C# console app on .NET 8 using the in-house
TC.MaintainanceTools.SimpleJobsframework (older 4.2 line) with AppSettings configuration and per-environmentappsettings.*.json. TC.Phenix.Services.Client7.49 overTC.ConnectionBroker.Wcf1.13 for the booking service;TC.ContactCentre.ServiceClientis referenced in the csproj though no direct usage was found in the job sources.- Nerdbank.GitVersioning for versioning, Scrutor for DI scanning, Newtonsoft.Json.
Deployment
Prod application with 1 release. Build pipeline job-update-credit-limit (YAML build.yaml using the shared /jobs/ci.yml pipeline template, .NET SDK 8.0.x) feeding release pipeline \finance\jobs\job-update-credit-limit CI. The README's deployment badges still point at unrelated "vibe-api" release definitions with a TODO to fix them.
Dependencies
- Internal NuGet packages:
TC.Phenix.Services.Client,TC.ConnectionBroker.*,TC.MaintainanceTools.SimpleJobs.*,TC.ContactCentre.ServiceClient,TC.Exceptions.WebApiClient. Hosting repos for these services could not be confidently matched to inventory names, so none are listed. - No external SaaS integrations.
Data stores
None accessed directly; customer balances live behind the Phenix/backoffice booking service.
Integration points
- WCF calls to the Phenix booking service via
TC.Phenix.Services.Client.BookingServiceReferenceand the connection broker, with exception notification through the internal exceptions web API client.
Code health
- Unit tests present (
UpdateCreditLimitJobTestswith fakes for the booking service and clock) and template-based YAML CI. - Least recently touched of the finance jobs reviewed: last commit 2025-06-27. README deployment section is stale.
Modernisation risks
- Pinned to older internal package lines (SimpleJobs 4.2, ConnectionBroker 1.13, Phenix client 7.49) than sibling jobs, so upgrades may need coordinated changes.
- WCF dependency on the legacy booking-service surface.
- Runtime and CI are modern; overall risk low for a small fallback job.