Fix response usage

[Alpaca131]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you read and signed the automated Contributor's License Agreement?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you lint your code locally prior to submission?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Alpaca131 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[grarich]

LGTM

[Alpaca131]

#66 Fixed this issue.

[blackduck-copilot]

Black Duck Security Report

Merging #67 into master will not change security risk.

Click here to see full report

[blackduck-copilot]

Black Duck Security Report

Merging #67 into master will not change security risk.

Click here to see full report

[shreyanshp]

Thank you @Alpaca131 and @solancer

[shreyanshp]

@Alpaca131

It seems your commit was not linked to the github account
Anyway I could see in cla-assistant that you did sign the cla so I will merge this for now