Closed jfloPMM closed 5 months ago
Hi @jfloPMM,
Looking through our logs, we have never received a successful POST
to create a background check for that user. I see three total requests. The first was at 2024-03-12T19:48:02.641Z
and the response was 403 Forbidden
. The Planning Center ID of the user making that request was 1781538
and while the error implies that they didn't have the correct permissions, that timing coincides with a bug that was identified on our end (reported here) which would have resulted in that same error.
Two additional POST
requests were made (at 2024-03-26T09:50:29.006Z
and 2024-03-27T16:12:07.646Z
). The response for both requests was 404 Not Found
. The Planning Center ID of the user making those requests was 1781538
, which is a different user in a different organization, so 404
is the expected response.
I would expect a POST
from the original user to work as expected. Please let us know if you have any other questions about this.
I followed up with the customer and he insists he is the admin in Planning Center and ran Sarah Jordan successfully in this same account. Is there something else I can do from my end to verify his user and what he is telling me?
Jennifer Fowler ministrybrands.comhttp://www.ministrybrands.com/ @.***
From: Shane Bonham @.> Sent: Wednesday, March 27, 2024 2:58 PM To: planningcenter/developers @.> Cc: Jennifer Fowler @.>; Mention @.> Subject: Re: [planningcenter/developers] Applicant badges in profile do not update consistently (Issue #1167)
CAUTION: This is an external email. Please use caution with links and attachments.
Hi @jfloPMMhttps://github.com/jfloPMM,
Looking through our logs, we have never received a successful POST to create a background check for that user. I see three total requests. The first was at 2024-03-12T19:48:02.641Z and the response was 403 Forbidden. The Planning Center ID of the user making that request was 1781538 and while the error implies that they didn't have the correct permissions, that timing coincides with a bug that was identified on our end (reported herehttps://github.com/planningcenter/developers/issues/1164) which would have resulted in that same error.
Two additional POST requests were made (at 2024-03-26T09:50:29.006Z and 2024-03-27T16:12:07.646Z). The response for both requests was 404 Not Found. The Planning Center ID of the user making those requests was 1781538, which is a different user in a different organization, so 404 is the expected response.
I would expect a POST from the original user to work as expected. Please let us know if you have any other questions about this.
— Reply to this email directly, view it on GitHubhttps://github.com/planningcenter/developers/issues/1167#issuecomment-2023723861, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXVREZX2KQSGI4HHAL35SC3Y2MJDNAVCNFSM6AAAAABFLHIK4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTG4ZDGOBWGE. You are receiving this because you were mentioned.Message ID: @.**@.>>
Hi @jfloPMM,
I don't think the problem is with the user account, but possibly the integration. The first request failed because of a defect on our end that was later resolved. The most recent two requests failed because they were not authenticated as the original user (who does have the correct permissions). They were authenticated with Planning Center organization ID 367034 and user ID 80722654. That organization appears to be a Protect My Ministry testing account. Since user ID 2951210 doesn't belong to that organization, the request resolved in a 404 Not Found
as expected.
Thanks for the info. That helps tremendously. When we were accessing his account using his credentials, the auto fill probably used our test account creds without us realizing it. I’ll have him reauthenticate the account.
Jennifer Fowler ministrybrands.comhttp://www.ministrybrands.com/ @.***
From: Shane Bonham @.> Sent: Thursday, March 28, 2024 10:40 AM To: planningcenter/developers @.> Cc: Jennifer Fowler @.>; Mention @.> Subject: Re: [planningcenter/developers] Applicant badges in profile do not update consistently (Issue #1167)
CAUTION: This is an external email. Please use caution with links and attachments.
Hi @jfloPMMhttps://github.com/jfloPMM,
I don't think the problem is with the user account, but possibly the integration. The first request failed because of a defect on our end that was later resolved. The most recent two requests failed because they were not authenticated as the original user (who does have the correct permissions). They were authenticated with Planning Center organization ID 367034 and user ID 80722654. That organization appears to be a Protect My Ministry testing account. Since user ID 2951210 doesn't belong to that organization, the request resolved in a 404 Not Found as expected.
— Reply to this email directly, view it on GitHubhttps://github.com/planningcenter/developers/issues/1167#issuecomment-2025383830, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXVREZSRQ5UIZACIZQZJKFDY2QTUBAVCNFSM6AAAAABFLHIK4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGM4DGOBTGA. You are receiving this because you were mentioned.Message ID: @.**@.>>
Affected Product People
Describe the bug One customer reports that intermittently (8 times so far) the badge does not update when the background check completes. It works for other applicants.
To Reproduce Steps to reproduce the behavior: Customer name- [REDACTED] User [REDACTED] Applicant Name [REDACTED] Applicant ID in Planning Center 2951210 Path [https://api.planningcenteronline.com/people/v2/people/2951210/background_checks] Third attempt 2024-03-27T12:12:07.5730000 Request { "data": { "attributes": { "report_url": [REDACTED], "result": "clear", "note": "If you have questions regarding the report or your account, contact support@protectmyministry.com" }, "type": "BackgroundCheck" } } Response time stamp 2024-03-27T12:12:07.6500000 Response details: {"errors":[{"status":"404","title":"Not Found","detail":"The resource you requested could not be found"}]} Response code 404
Expected behavior badge should update to Clear/green
Screenshots attached![Screenshot 2024-03-14 at 9 02 26 AM](https://github.com/planningcenter/developers/assets/99291750/e48922e1-c469-4df5-a3ea-113c582d2047)
Additional Context:
Additional context
I have..