Unable to fetch slack messages due to incorrect timestamp format

[abhi1693]

Bug Description

The Slack Conversations History API returns no messages if the latest or oldest timestamps include decimal places. However, the API returns the expected messages if the timestamps are provided without any decimal places.

To Reproduce

Steps to reproduce the behavior:

1. Call the Slack API using the following URL with decimal places in the timestamps:

https://slack.com/api/conversations.history?channel={channel_id}&limit=200&oldest=1718641354.561659&latest=1734193354.5616593

2. Observe that no messages are returned in the response.
3. Call the Slack API using the following URL without decimal places in the timestamps:

https://slack.com/api/conversations.history?channel={channel_id}&limit=200&oldest=1718641354&latest=1734193354

4. Observe that messages are successfully returned.

Expected behavior

The API should return messages that are then added to the index.

Screenshots

Environment

• OS: [e.g. iOS] docker.elastic.co/integrations/elastic-connectors:8.17.0
• Browser [e.g. chrome, safari] NA
• Version [e.g. 22] 8.17.0

Additional context

[seanstory]

Sounds like you've found a bug in the Slack API, not in the connector. Looking at https://api.slack.com/methods/conversations.history#arg_oldest, I see that decimal format is the example, so it should be expected to work.

Have you raised this issue with Slack?