Why Does the Firebase Console Query Builder Alter Timestamp Precision in Firestore Queries?

I observed inconsistent results between Firestore queries executed in my code and those built using the Firebase Console Query Builder when filtering timestamps.

My code returns 13 documents when filtering on the 'create_on' field, but the Web UI returns 0. Here is an example of the timestamp filters as used in the query:

startDate.toDate() = "2025-01-01T03:00:00.000Z"
endDate.toDate() = "2025-02-01T02:59:59.999Z"

The code performing the query looks like this:

JAVASCRIPTCopied
const querySnapshot = await transaction.get(
  db
    .collection('Coll_Name')
    .where('period_type', '==', periodType)
    .where('entity_id', '==', entity.id)
    .where('entity_type', '==', 1)
    .where('main_entity_id', '==', main_entity.id)
    .where('create_on', '>=', startDate)
    .where('create_on', '<=', endDate),
);

console.log('after querySnapshot');

console.log(
  `Found ${querySnapshot?.docs?.length > 1 ? 'many' : 'some'}
    `,
);

console.log('Length: ', querySnapshot?.docs?.length);  // 13 docs here

Without filtering on the 'create_on' field, 41 documents are returned. However, applying the exact same filters via the Firebase Console UI yields 0 documents.

Inspecting the network requests shows that the timestamp values actually sent differ slightly in milliseconds precision:

{
    "fieldFilter": {
      "field": { "fieldPath": "create_on" },
      "op": "GREATER_THAN_OR_EQUAL",
      "value": {
        "timestampValue": "2025-01-01T03:00:00.027000000Z"
      }
    }
  },
  {
    "fieldFilter": {
      "field": { "fieldPath": "create_on" },
      "op": "LESS_THAN_OR_EQUAL",
      "value": {
        "timestampValue": "2025-02-01T02:59:59.884000000Z"
      }
    }
  }

Notably, decreasing the start date by 1 second returns the 13 expected documents. It seems that minor differences in timestamp precision between the Date objects provided in the SDK and the values used by the Console Query Builder lead to this discrepancy.

Is there a way to align these timestamp precisions or otherwise work around this behavior?