DROP - Issues and Resolutions

Owned by Meet Shah
Last updated: May 30, 2024 by Matthew Hall
2 min read

Setup Local ENV

The steps are well documented in the Github Wiki Home · bcgov/PaymentCommonComponent Wiki (github.com)

Access Report from AWS

Login to https://login.nimbus.cloud.gov.bc.ca/api
Click on 953134788580 - iz8ci7-prod, This will open a drop down
Click on Login to Console, AWS Console will open in a new tab
Search for S3 in the top navigation bar
Open “pcc-recon-reports-prod” bucket

The reports are generated everyday with past 30 days of data
Sort the listing by “Last Modified” Date Column or Search for the report with prefix “reconciliation_report_YYYY-MM-DD“ replace YYYY-MM-DD with start date.

Create Report Download URL

  1. Follow the steps above to get to the “pcc-recon-reports-prod” bucket.

  2. click the report name, and then click Object Actions, and Share via presigned url

  3. fill in for the max expiry you will get the url (copied to your clipboard).

image-20240509-165246.png

The url is nice since the file is so big it is easier to share, just make sure to tell whoever it is shared with to save the actual downloaded file somewhere, because the url itself will expire.

Issue while sending Email (fixed)

We are using GC Notify Integrate the API | GC Notify to send reports and alerts by email
While sending the email, we are getting an error “Invalid token: Enter your full API key”
The KEY was working earlier as we have few emails that were sent successfully in past
Because of this error, no alerts or reports are sent by email

As a resolution, new Authorization Key must be generated and updated in the AWS Parameter store (/pcc/.env) and All Lambda Functions ENV Variable (MAIL_SERVICE_KEY)

Issue in generating Report

While processing a file (PROD_SBC_F08TDI17_20240325.DAT) received in March
We found a new listing “Mobile Service Centre Van”
The current code is supposed to process only cash and cheque records, this record is little different then the expected one
Due to the difference in record, the code broke at that point and the report is not generated

There are 2 possibilities to fix this problem:

  • Remove such records before sending the file

  • Modify code to skip/process the record