Skip to content

Troubleshooting

Having many mocks set up within a single workspace may cause some overlapping of matches. Complex templates/code may also raise some unexpected behavior, like errors thrown during the processing of the request or invalid response content rendered. The primary tools to handle such situations are Workspace Test and Request Log. These tools provide insight into request content, output and order of matching mocks, template logs, dynamic mocks, and response content. In most situations, the provided data helps to solve the issues with matching and response rendering.

Error Outputs

In some situations, the mock consumer may not get the expected response. Instead, the response with a text/plain Content-Type and an error message is returned. This may happen when SmartMock.io is not able to serve the request due to invalid requests, incorrect mock template/code, exceeded quota, or other internal errors. The following error messages may be returned:

  • Domain not found. Please verify the workspace configuration and try again. - DOMAIN_NOT_MATCHED - The workspace with the requested subdomain cannot be found. Please verify the workspace exists and that your account is not locked. Try again in 5 minutes. If the problem persists, please contact our support.

  • The monthly request quota exceeded. - MONTHLY_QUOTA_EXCEEDED - Requests can’t be served because the monthly request quota has exceeded. Upgrade your subscription or wait until your quota replenishes at the beginning of the next calendar month. If you have any questions about quota usage, please contact our support.

  • Too many concurrent requests. - TOO_MANY_CONCURRENT_REQUESTS - The request was not processed because there were other concurrent requests to workspaces belonging to the same account in progress, and the number of these requests was equal to the concurrent request quota for the account. If you have any questions about quota usage, please contact our support.

  • Request body too large. - REQUEST_TOO_LARGE - The request sent by the mock consumer was too large. See the Limits section to check the maximum request size.

  • The response generated by the template or code too large. - RESPONSE_TOO_LARGE - See the Limits section to check the maximum response size.

  • State generated by template or code too large. - STATE_TOO_LARGE - See the Limits section to check the maximum serialized state size.

  • No matched mocks. - MOCKS_NOT_MATCHED - There was no mock matched for the request. Please check the Request Log for more details. You may also test matching logic using the Workspace Test feature.

  • Code or template execution exceeded maximum invocation time. - EXECUTION_TIMEOUT - This may happen, for example, when an infinite loop is encountered within the code. Please check your code for such issues. If the problem persists, please contact our support.

  • There was an error during the execution of the mock code. - CODE_ERROR or TEMPLATE_ERROR - The template or code of the mock is invalid. Please check the Request Log for more details. You may also test mock template/code using the Workspace Test feature.

  • Dynamic mocks execution environment not ready. Please check the administration console or contact our support. - EXECUTION_ENVIRONMENT_NOT_READY - Runtime, which executes mocks templates or code, is not ready to serve the request. Please log in to your account and navigate to Workspace Details to re-enable execution runtime. Please try again in 10 minutes or contact our support if the problem persists.

  • The proxy call timed out. - PROXY_CALL_TIMEOUT - Call from SmartMock.io to destination service timed out. Please check if destination service is up and running or adjust request timeout value in the mock settings.

  • Proxy call connection error. - PROXY_CONNECTION_ERROR - Cannot establish a TCP connection between SmartMock.io and destination service. Please check if destination service is up and running or adjust request timeout value in the mock settings.

  • Proxy destination responded with an invalid HTTP response. - PROXY_HTTP_ERROR - The destination service failed to reply with a valid HTTP response.

  • Invalid proxy target URL. - PROXY_INVALID_URL - Proxy target URL is incorrect. Please review the mock proxy settings and try again.

  • Detected cycle in the proxy request. - PROXY_CYCLE_DETECTED - This error appears when SmartMock.io is configured to proxy requests to itself. Please check the mock configuration.

  • Your current plan does not support this type od mocks. - MOCK_TYPE_NOT_SUPPORTED - Your current plan does not support this type of mocks. Please check your active plan details in the Plan & Billing view, update subscription and try again.

  • Your current plan does not support simulation of faults. - FAULTS_NOT_SUPPORTED - Your current plan does not support simulation of faults. Please check your active plan details in the Plan & Billing view, update subscription and try again.

  • Your current plan does not support response delays. - DELAYS_NOT_SUPPORTED - Your current plan does not support response delays. Please check your active plan details in the Plan & Billing view, update subscription and try again.

  • Your current plan does not support proxy mocks. - PROXY_NOT_SUPPORTED - Your current plan does not support proxy mocks. Please check your active plan details in the Plan & Billing view, update subscription and try again.

  • An unknown error has occurred. Please try again later or contact our support - UNKNOWN_ERROR - There was an unknown error while processing the request. Please try again in a few minutes or contact our support.

Last update: June 30, 2020