Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Troubleshoot ERR_BAD_REQUEST #117

Closed
mtuchi opened this issue Jan 15, 2024 · 2 comments · May be fixed by #119
Closed

Troubleshoot ERR_BAD_REQUEST #117

mtuchi opened this issue Jan 15, 2024 · 2 comments · May be fixed by #119
Assignees

Comments

@mtuchi
Copy link
Collaborator

mtuchi commented Jan 15, 2024

Description

  1. This timer job has been failing repeatedly over the last week - see run. Error is showing 401
  2. We have not edited the job, nor have we edited the credential… so I’m not sure why it’s failing now. Also, with this username and password, I can log into the CommCare web UI just fine… so I’m wondering if maybe the CommCare API access/permissiosn changed… but the client is not sure.
  3. To test, can you please try running this job locally to troubleshoot? I will DM you the configuration
  4. If you get it working locally --> then please fix the job on platform. If the job is NOT working locally, then please let Hildah know… I have cc’d you on the email with her. Either way, please follow up with her and try to resolve this ASAP.
@mtuchi mtuchi changed the title Troubleshoot Authorization Troubleshoot ERR_BAD_REQUEST Jan 15, 2024
@mtuchi mtuchi self-assigned this Jan 15, 2024
@mtuchi
Copy link
Collaborator Author

mtuchi commented Jan 15, 2024

After investigating the recent job failure, I've identified the issue causing the disruption. The Commcare baseURL now requires a trailing slash.

To fix this,We need to update the Commcare LIVE Digital Systems Admin credentials on OpenFn. Ensure that the baseUrl is appended with a trailing slash. For example:

baseUrl: https://www.commcarehq.org/a/lwala-community-alliance/api/v0.5/case/

I checked Commcare's changelog but found no mention of this alteration. However, before January 11, the job functioned well without requiring a trailing slash. It's possible that Commcare updated their server configuration, leading to the necessity of a trailing slash.

cc @aleksa-krolls Aissa

@mtuchi
Copy link
Collaborator Author

mtuchi commented Jan 16, 2024

Closing this as it was resolved by adding a trailing slash on baseUrl

@mtuchi mtuchi closed this as completed Jan 16, 2024
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 a pull request may close this issue.

1 participant