Skip to content

[jumpcloud]: Start time can be later than End time. #17209

@StacieClark-Elastic

Description

@StacieClark-Elastic

Integration Name

JumpCloud [jumpcloud]

Dataset Name

events

Integration Version

1.17.0

Agent Version

NA integration issue

Agent Output Type

elasticsearch

Elasticsearch Version

NA integration issue

OS Version and Architecture

NA integration issue

Software/API Version

NA integration issue

Error Message

failed to collect first response: failed to execute http POST: server responded with status code 400 Bad Request: {"message":"Start Time not after End Time 2026-01-26T09:13:52Z \u003e 2026-01-26T09:11:52Z"}

Event Original

No response

What did you do?

NA

What did you see?

NA

What did you expect to see?

Expected start time to be less than end time

Anything else?

Lag time was added for this version 1.17.0: #15248
There are conditions under which the start time can be later than or equal to the end time.

failed to collect first response: failed to execute http POST: server responded with status code 400 Bad Request: {"message":"Start Time not after End Time 2026-01-26T09:13:52Z \u003e 2026-01-26T09:11:52Z"}
and ingestion stops, where the End time is N minutes before than the Start Time.

In the above log Source Lag time parameter was set to 2m with the cursor set to null.
When Source Lag Time was set to zero, the the same error only with identical timestamps for Start Time and End Time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Integration:jumpcloudJumpCloud (Community supported)Team:Sit-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]maintainer:CommunityCommunity supported integrationneeds:triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions