> ## Documentation Index > Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Data Provider Status Messages ## Data Provider Status Messages Lendflow records a status for each external data-service request. Use these statuses to determine whether a service has not started, is still running, completed successfully, found no matching record, or requires corrective action. Some messages come directly from the provider. Others are normalized by Lendflow so common failures are easier to understand. ## Where provider statuses appear The [Get Commercial Data](/api-reference/workflow-management/get-commercial-data) response returns `data.statuses` alongside `data.commercial_data` and `data.request_data`. Statuses are grouped by provider and, when applicable, by service. Use the optional repeated `services[]` query parameter to limit the response to specific services. ```json theme={"system"} { "data": { "commercial_data": { "experian": {} }, "statuses": { "experian": { "business_match": "Success" }, "middesk": "Not yet started" } } } ``` The Lendflow Dashboard reads the same service statuses when it displays a data-service block on a deal. Depending on the service and result, the dashboard may: * Display the status message as returned. * Present a no-results state instead of the raw message. * Replace a technical provider response with clearer Lendflow wording. * Continue showing the most recent successful response while identifying that the latest request failed. Data Orchestration also records workflow-level failures in the orchestration log's `internal_error` field. That field describes a failed orchestration run and is separate from the provider statuses documented here. ## Standard lifecycle statuses | Status | Meaning | | - | - | | `Not yet started` | The service has not been run for the application. | | `Started` | Lendflow accepted the request and the service is still processing it. | | `Success` | The service completed without a request-level failure. Review the corresponding provider data for the result. | Some providers also return an in-progress message: | Provider | Status | | - | - | | Baselayer | `Baselayer NaicsPrediction Requested` | | Baselayer | `Baselayer WebsiteAnalysis Requested` | | Baselayer | `Baselayer Enhanced Requested` | | Baselayer | `Baselayer Pep Requested` | ## Interpret status messages | Category | What it means | Common action | | - | - | - | | **Lifecycle** | The service has not started, is processing, or completed successfully. | Wait for an in-progress request or review the returned data after Success. | | **No result** | The request completed, but the provider did not find a matching person, business, or record. | Verify the submitted information. Run the service again only after correcting or adding information. | | **Input or prerequisite** | Required application information, documents, or service options are missing or invalid. | Correct the specified field or prerequisite, then run the service again. | | **Retryable** | The provider timed out or reported a temporary availability problem. | Wait and retry. Contact Lendflow if the failure continues. | | **Configuration** | Credentials, certification, provider access, or a required provider configuration is unavailable. | Contact your Lendflow account manager or administrator. | | **System or provider error** | The provider or integration returned an unexpected error. | Record the application, provider, service, and message, then contact Lendflow if retrying does not resolve it. | Do not retry every failure automatically. Correct input and prerequisite errors first, and escalate configuration errors instead of repeatedly running the service. ## Provider-specific messages Text in braces or brackets is dynamic and changes with the application, provider response, request, or service. ### Experian | Status | Category | Meaning or action | | - | - | - | | `No Business found - {business_legal_name}` | No result | Experian did not find a business matching the submitted information. Verify the legal name and other business details. | | `Error while searching for Business {business_legal_name}: {provider_error}` | System or provider error | Experian returned the appended provider error while searching for the business. | | `Something went wrong. Try again later` | System or provider error | The request failed without a more specific response. Retry later and escalate if it continues. | | `The service did not respond within a reasonable time. Try again later.` | Retryable | Experian did not respond before the request timed out. | | `There is currently a problem retrieving data from Experian. For support please contact your account manager.` | Configuration | The required Experian configuration is unavailable. Contact your account manager. | | `Business owner SSN is required.` | Input or prerequisite | Add the owner's SSN before running the applicable report. | | `A valid, 9-digit business owner SSN is required.` | Input or prerequisite | Correct the owner's SSN. | | `SSN field must be a valid SSN or ITIN of business owner.` | Input or prerequisite | Supply a valid SSN or ITIN for the owner. | ### Middesk | Status | Category | Meaning or action | | - | - | - | | `Middesk: cannot create business - {validation_errors}` | Input or prerequisite | Correct the application fields identified after the message prefix. | ### Ekata | Status | Category | Meaning or action | | - | - | - | | `Ekata completely failed for application [{application_id}]` | System or provider error | Every Ekata inquiry in the request failed. Retry and escalate if the failure continues. | ### Ocrolus | Status | Category | Meaning or action | | - | - | - | | `The service did not respond within a reasonable time. Try again later.` | Retryable | Ocrolus did not respond before the request timed out. | | `Uploaded bank statements are required to perform CFA` | Input or prerequisite | Upload bank statements before running Cash Flow Analysis. | | `Uploaded bank statements must be of type PDF for running Ocrolus CFA` | Input or prerequisite | Replace unsupported files with PDF bank statements. | ### LexisNexis | Status | Category | Meaning or action | | - | - | - | | `No search results found.` | No result | LexisNexis found no record matching the submitted information. | | `No contact card results found.` | No result | The contact-card search returned no matching result. | | `No RiskView attributes were returned.` | No result | The RiskView request returned no attributes. | | `The service did not respond within a reasonable time. Try again later.` | Retryable | LexisNexis did not respond before the request timed out. | | `Something went wrong while processing the request.` | System or provider error | The request failed without a more specific response. | | `Authorization failed.` or `Unauthenticated.` | Configuration | Provider authentication failed. Contact your Lendflow account manager or administrator. | ### Clear | Status | Category | Meaning or action | | - | - | - | | `Something went wrong while searching.` | System or provider error | Clear returned an unexpected search failure. | | `Business owner {field} is required.` | Input or prerequisite | Add the required owner field. | | `Business owner {field} must be a string.` | Input or prerequisite | Correct the format of the specified owner field. | | `Business owner {field} is not valid.` | Input or prerequisite | Correct the specified owner value. | An empty Clear result can be recorded as `Success`. Review the Clear data in addition to the status before determining whether a match was found. ### Equifax | Status | Category | Meaning or action | | - | - | - | | `Something went wrong while searching.` | System or provider error | Equifax returned an unexpected search failure. | | `No search results found: {hitcode_description}.` | No result | Equifax did not find a record matching the submitted information. | | `Vermont files blocked` | Configuration | Additional Equifax certification is required for Vermont files. | | `This area of records temporarily unavailable - please try later` | Retryable | The requested records are temporarily unavailable. | | `Address is misspelled or not in ACROPAC system` | Input or prerequisite | Correct the city, state, or address information. | | `Invalid last name` | Input or prerequisite | Correct the individual's last name. | | `Invalid first name` | Input or prerequisite | Correct the individual's first name. | | `Please review the individual information for invalid characters and try to run again` | Input or prerequisite | Remove invalid characters from the individual's information before retrying. | ### DNB | Status | Category | Meaning or action | | - | - | - | | `DNB service DUNS lookup, error: {provider_error}` | Input, no result, or provider error | Review the appended DNB response. This prefix can represent validation failures or provider errors and does not always mean that no match exists. | | `DNB service Name and Address Lookup, error: {provider_error}` | Input, no result, or provider error | Review the appended DNB response and correct submitted information when indicated. | ### MoneyThumb | Status | Category | Meaning or action | | - | - | - | | `Something went wrong while processing the request.` | System or provider error | The request failed without a more specific response. | | `The service did not respond within a reasonable time. Try again later.` | Retryable | MoneyThumb did not respond before the request timed out. | | `Uploaded PDF bank statements are required to perform CFA` | Input or prerequisite | Upload PDF bank statements before running MoneyThumb Cash Flow Analysis. | ### Codat | Status | Category | Meaning or action | | - | - | - | | `Accounting: Codat failed request [{request_name}] for application [{application_id}]` | System or provider error | The named Codat request failed for the application. | ### Rutter | Status | Category | Meaning or action | | - | - | - | | `Commerce: Rutter failed request [{request_name}] for application [{application_id}]` | System or provider error | The named Rutter request failed for the application. | ### TaxStatus | Status | Category | Meaning or action | | - | - | - | | `Something went wrong while searching.` | System or provider error | TaxStatus returned an unexpected search failure. | | `Taxpayer not found.` | No result | TaxStatus did not find the taxpayer. Verify the submitted taxpayer information. | | `Waiting on IRS` | Retryable | TaxStatus is waiting for the IRS to provide the record. Retry after the record becomes available. | | `IRS system down` | Retryable | The IRS system is temporarily unavailable. Retry later. | ## What to do when a service fails 1. Identify the provider and specific service under `statuses`. 2. Copy the complete status message, including any dynamic provider details. 3. Check the corresponding request data for missing or incorrectly formatted information. 4. Complete any missing prerequisite, such as uploading PDF bank statements. 5. Retry only when the message indicates corrected input or a temporary provider problem. 6. If the problem continues, contact Lendflow with the application ID, provider, service, timestamp, and complete message. When the Dashboard continues showing an older successful response, treat the displayed data as historical. The error message describes the latest attempt. ## FAQ The Dashboard may replace technical provider text with clearer Lendflow wording or a dedicated no-results state. Use the API's `statuses` value when reporting the complete technical message. No. Success means the request completed without a request-level failure. Some services can return an empty result, so review the corresponding provider data as well. No. Correct input and prerequisite errors first. Retry temporary availability problems after waiting. Escalate authentication, certification, or configuration errors to your Lendflow account manager or administrator. The Dashboard can preserve the most recent successful response while identifying that the latest request failed. Review the status and request timestamp before using the displayed data. They are placeholders for dynamic information, such as an application ID, business name, provider error, or request name. The returned status contains the actual value.