Closed jakedouglas closed 2 years ago
Mike deliberately put in BAD Pepco credentials. We know that those come back as an ERROR from the scraper.
But his webhook showed accounts_load_in_progress: true:
accounts_load_in_progress: true
[0] Received a webhook with data: [0] { [0] type: 'utility_credential_verification_error', [0] created_at: '2021-09-29T12:50:33.824-04:00', [0] data: { [0] id: 1801, [0] username: 'email@gmail.com', [0] created_at: '2021-09-29T12:50:30.947-04:00', [0] updated_at: '2021-09-29T12:50:33.213-04:00', [0] utility_name: 'Pepco', [0] client_user_id: '88181', [0] verification_status: 'error', [0] verification_updated_at: '2021-09-29T12:50:33.209-04:00', [0] accounts_load_in_progress: true [0] } [0] }
We need to fix this in the serializer to look at the DERIVED verification_status or otherwise consider that it's in a retrying state.
verification_status
Reposted to Jira here https://arcadiapower.atlassian.net/browse/EN-669 - closing this issue since we know where this bug is exactly and it isn't quickstart
Mike deliberately put in BAD Pepco credentials. We know that those come back as an ERROR from the scraper.
But his webhook showed
accounts_load_in_progress: true
:We need to fix this in the serializer to look at the DERIVED
verification_status
or otherwise consider that it's in a retrying state.