Forums - Thread Details
  • State Not Answered
  • Replies 9 replies
  • Subscribers 12 subscribers
  • Views 6301 views
  • Users 0 members are here
Related

GoFileRoom "Retrieve document indexes" API endpoint returns results from a different tenant

Ian Cranston

I have encountered an issue where GoFileRoom's Retrieve document indexes endpoint replies with index data from a different tenant. The issue occurs infrequently, but I've been able to log it happening twice recently.

Below is the log for querying the index of filingID 000000T5W1. Note that the first response is a file for a different tenant that uses a different client ID syntax (index 2) and differently ordered indexes (indexes 6 and 7). Upon immediate and subsequent re-querying the correct index response is received.

3/28/2025 3:09:13 PM
DEBUGGING: Detected a bad year index in Get-DocDetails
filingID: 000000T5W1
@{indexId=0000000002; indexValue=21650}
@{indexId=0000000003; indexValue=INDIVIDUAL TAX}
@{indexId=0000000004; indexValue=TAX RETURN}
@{indexId=0000000005; indexValue=2018 CLIENT ACTION PAGES}
@{indexId=0000000006; indexValue=12/31}
@{indexId=0000000007; indexValue=2018}
@{indexId=0000000008; indexValue=2019-04-02}

Trying again immediately...
3/28/2025 3:09:13 PM
@{indexId=0000000002; indexValue=20099.002}
@{indexId=0000000003; indexValue=AUDIT}
@{indexId=0000000004; indexValue=FINANCIAL STATEMENT / DELIVERABLES}
@{indexId=0000000005; indexValue=FINANCIAL STATEMENT WORD}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-03-28}

Sleeping and trying again...
3/28/2025 3:09:19 PM
@{indexId=0000000002; indexValue=20099.002}
@{indexId=0000000003; indexValue=AUDIT}
@{indexId=0000000004; indexValue=FINANCIAL STATEMENT / DELIVERABLES}
@{indexId=0000000005; indexValue=FINANCIAL STATEMENT WORD}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-03-28}

Sleeping and trying again...
3/28/2025 3:09:49 PM
@{indexId=0000000002; indexValue=20099.002}
@{indexId=0000000003; indexValue=AUDIT}
@{indexId=0000000004; indexValue=FINANCIAL STATEMENT / DELIVERABLES}
@{indexId=0000000005; indexValue=FINANCIAL STATEMENT WORD}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-03-28}

Here is a second incident querying the index of filingID 000000T9M2.

4/2/2025 10:21:49 AM
DEBUGGING: Detected a bad year index in Get-DocDetails
filingID: 000000T9M2
@{indexId=0000000002; indexValue=16353}
@{indexId=0000000003; indexValue=INDIVIDUAL TAX}
@{indexId=0000000004; indexValue=CARRYFORWARD INFORMATION}
@{indexId=0000000005; indexValue=}
@{indexId=0000000006; indexValue=12/31}
@{indexId=0000000007; indexValue=2018}
@{indexId=0000000008; indexValue=2019-04-06}

Trying again immediately...
4/2/2025 10:21:49 AM
@{indexId=0000000002; indexValue=18469.001}
@{indexId=0000000003; indexValue=1040 INDIVIDUAL TAX}
@{indexId=0000000004; indexValue=TAX RETURN}
@{indexId=0000000005; indexValue=CLIENT COPY}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-04-02}

Sleeping and trying again...
4/2/2025 10:21:55 AM
@{indexId=0000000002; indexValue=18469.001}
@{indexId=0000000003; indexValue=1040 INDIVIDUAL TAX}
@{indexId=0000000004; indexValue=TAX RETURN}
@{indexId=0000000005; indexValue=CLIENT COPY}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-04-02}

Sleeping and trying again...
4/2/2025 10:22:25 AM
@{indexId=0000000002; indexValue=18469.001}
@{indexId=0000000003; indexValue=1040 INDIVIDUAL TAX}
@{indexId=0000000004; indexValue=TAX RETURN}
@{indexId=0000000005; indexValue=CLIENT COPY}
@{indexId=0000000006; indexValue=2024}
@{indexId=0000000007; indexValue=12/31}
@{indexId=0000000008; indexValue=2025-04-02}

  • 0

    Does anyone know how to reach the right people at TR about this? Seems like a big deal. GoFileRoom is sometimes replying with data from a different CPA.

  • 0
    Thomson Reuters Thomson Reuters staff member
    in reply to Ian Cranston

     Hi  

    Could you please provide and assist us with the following information?

    1.What is the GFR Database ID?
    2.Provide the steps to replicate the issue?
    3.Why was the same document ID called multiple times, and what type of document was involved?

    Thank You.

  • 0 in reply to Krishna Pendyala

    Hello Krishna,

    Krishna Pendyala said:
    1.What is the GFR Database ID?

    The document filingIDs for two example files are listed in my original post in bold. Please let me know if I'm misunderstanding what you're asking for.

    Krishna Pendyala said:
    2.Provide the steps to replicate the issue?

    I am unable to replicate the issue. I can only catch it when it occurs roughly every 1-3 days while using the Retrieve document indexes​ API endpoint.

    Krishna Pendyala said:
    3.Why was the same document ID called multiple times

    For troubleshoot purposes. In the first attempt, the API replies with the wrong index information, in the subsequent attempts, the correct index information is returned.

    Krishna Pendyala said:
    and what type of document was involved?

    The index information is listed in my post. If you're looking for something else, please let me know.

  • 0
    Thomson Reuters Thomson Reuters staff member
    in reply to Ian Cranston

    Hi   ,

    The team was reviewing this item and had a question.  "The API expects a documentID as a parameter, but they are passing a filingID.  How and why are they passing a FilingID for this call"

  • 0 in reply to Krishna Pendyala

    I erroneously called it a filingID in my post. It's a documentID.

  • 0
    Thomson Reuters Thomson Reuters staff member
    in reply to Ian Cranston

    Hi  , I hope this message finds you well. We are currently facing challenges in reproducing the issue related to the API and would appreciate your help in obtaining further information. Could you please provide the following details?

    1. Recent Reports: Are there any recent reports or instances of this issue that could help us understand it better?

    2. Documentation/Indexes: Do you have any additional documents or indexes that might serve as useful references for our investigation?

    3. Login ID: Could you share the login ID that was used to call the API?

    4. API Call Method: How are the API calls being made? Are they executed using tools like Postman, other automation tools, or a custom utility developed internally?

    Your cooperation in providing these details will greatly assist us in resolving the issue efficiently. Thank you for your support.

  • 0 in reply to Krishna Pendyala

    1. Yes - I've been sending them to you in our DM as they occur. Last occurrence was 5/6/2025 11:07:48 AM

    2. Yes - I've been sending the documentID/index information as incidents occur in our DM.

    3. I will send this to you now in our DM.

    4. API calls are being made with a custom utility developed internally. 

  • 0
    Thomson Reuters Thomson Reuters staff member
    in reply to Ian Cranston

    Hi , Could you please look into this and  provide the following details?

    We are trying to recreate the scenario in our lower environment. I would like to have more info on how the custom utility works.

      Step 1: Creating Authentication Token - Are you calling the end point v1/user/login with user credentials corresponding to        email  and generating token
      Step 2: Make a call to v1/documents/{{documentId}}/indexes
      Step 3: As the index didn't match, are you reusing the same token created in step 1 or are you creating new token?

     

    Is there any caching enabled in the custom utility? If YES, what data are you caching? What the expiry of cache?
    Are getting wrong data for any other APIs?
    How frequently this data mismatch happens?

  • 0 in reply to Ramamohan Rao Immanni

    See my DM