Do Appflow Slack Filters Work For Anyone?

Question

This may be a repeat question of this post:
https://repost.aws/questions/QUtE5aFQKUT-uF_kMllwGaYA/amazon-appflow-for-slack

But every time I go to set up a filter for a Slack flow in Appflow, I can successfully add it, but looking at record counts after running the flow, nothing get's filtered out. I've tried different formats of Unix timestamp and different/varied look back periods with no changes to the flow runs. Everything is up to date on the connection and I otherwise don't have an issue pulling all records from the connection. My best guess is that because the timestamp value is showing up as a string datatype now (the sample video from the link above shows it as a date value) and the filter expects a date value, the filter won't work regardless of Unix formatting

Is this working for anyone? Is the timestamp value for your slack records a string value or is this just me?

re:Post Agent · Answer

There appears to be an issue with the timestamp filtering functionality in Amazon AppFlow for Slack connections. Based on available information, you're not alone in experiencing this problem.

The issue seems to be that while the timestamp filter should work for filtering Slack messages based on date, there's a discrepancy where the timestamp is being treated as a string type rather than a date type. This matches what you've observed - the filter can be added but doesn't actually filter out any messages, regardless of the Unix timestamp format used.

This appears to be a technical issue with the AppFlow Slack connector rather than a configuration problem on your end. The timestamp field showing as a string instead of a date type (as shown in documentation examples) is likely preventing the filter from functioning correctly.

For large message volumes like you're dealing with, this is particularly problematic since AppFlow will attempt to process all messages in the channel rather than just the ones within your desired timeframe.

Since this seems to be a service issue rather than user error, you might want to:
1. Contact AWS Support directly for assistance
2. Consider implementing a workaround such as processing all data and then filtering it at the destination
3. Monitor for any service updates that might address this issue

Unfortunately, there's no clear solution available at this time for making the timestamp filters work correctly with Slack as a source in AppFlow.  
**Sources**  
[Amazon AppFlow for Slack | AWS re:Post](https://repost.aws/questions/QUtE5aFQKUT-uF_kMllwGaYA/amazon-appflow-for-slack)  
[Slack - Amazon AppFlow](https://docs.aws.amazon.com/appflow/latest/userguide/slack.html)  
[Amazon AppFlow flows - Amazon AppFlow](https://docs.aws.amazon.com/appflow/latest/userguide/flows.html)

Do Appflow Slack Filters Work For Anyone?

Add your answer

Relevant content