Messaging Documentation
API Docs
  • Introduction
  • Getting started
    • Transitioning from v2 to v4
  • Message structure
    • Entity messages
      • Message group
      • Action
      • Example messages
    • Configuration messages
      • Message group
      • Action
      • Example messages
    • Financial messages
      • Message group
      • Action
      • Example messages
    • Batch Messages
      • Message group
      • Action
      • Example messages
  • Sample projects
  • Message metrics
  • FAQ
  • SQS - Queues
    • Overview
    • Setting up an SQS message integration
    • SQS queue names
  • SNS - PUB/SUB
    • Overview
    • Setting up an SNS message integration
    • SNS topic names
    • Message attributes
  • 🆕EventBridge
    • Overview
    • Setting up an EventBridge integration
Powered by GitBook
On this page

Was this helpful?

  1. SQS - Queues

Overview

These queues are best when there is only one consumer. All char types and actions are represented on the FIFO queue. Acknowledgement of the message is necessary in order to take the message off the queue. If no acknowledgement is received, the message is placed back onto the queue.

Our queues adhere to the following:

  1. Each queue is set to the SQS FIFO queue defaults: visibility timeout is 30 seconds, and maximum message retention period is 4 days.

  2. Since these are FIFO queues, maximum inflight messages per queue is 20,000. If that limit is hit, you won’t receive any overlimit errors (unlike Standard queues).

  3. There is no dead letter or redrive policy set up on these queues; which means you can receive messages as many times without deleting them.

PreviousFAQNextSetting up an SQS message integration

Last updated 4 years ago

Was this helpful?