Troubleshooting segments - Amazon Pinpoint
Segment import failedSegment export failedEndpoint count for a dynamic segmentBadRequestException: Exceeded maximum endpoint per user count: 15BadRequestException when calling the UpdateEndpointsBatch or UpdateEndpoints operation: Too many custom attributes

Troubleshooting segments

Verify that logging is turned on to assist in identifying the cause of failure. For more information, see Monitoring and logging.

Segment import failed

If a segment import fails, you may see the following error message or similar:

Import job: Import failed for file SampleTemplate.csv with segment name SampleTemplate. Bad request: The data we received didn't match the format we expected for the createImportJob operation. Confirm that the information in your request is formatted properly, and then submit your request again.

Issue and solution

  • This error occurs when the imported template is not formatted correctly.

  • Verify that the template is in valid JSON or CSV format. See Segment files for an example of the correct format. A sample template can also be downloaded from the Console. Under your project, select Segments, Create a segment, Import a segment, and select Download example CSV.

  • Verify that all specified attributes are valid. ChannelType and address are required fields when importing segments. Attribute names are case-sensitive. For a complete list of possible attributes that can be added to a template, see Supported attributes.

Segment export failed

Issue and solution

  • Large export jobs may fail when performing this action from the console.

  • As a workaround for this limitation, the segment can be exported to an Amazon S3 bucket using the CreateExportJob API through the command line reference (CLI) or SDK.

Endpoint count for a dynamic segment

Issues and solutions

  • When using a dynamic segment to create a campaign, the number of endpoint count is an approximation and may not be accurate. This is because endpoint data in dynamic segments are subject to change over time based on the defined criteria. The segment can be exported to confirm the exact number of endpoints at a given point in time.

BadRequestException: Exceeded maximum endpoint per user count: 15

This error occurs when attempting to add more than 15 endpoints associated with the same UserId.

Note

If the new endpoint has a channel type of ADM, GCM, APNS, APNS_VOICE, APNS_VOIP_SANDBOX, or BAIDU, the request will succeed if there's already an endpoint with one of those channel types. For more information, see Managing an audience members maximum number of endpoints in the Amazon Pinpoint Developer Guide.

Issue and solution

  • You might see this error when creating new endpoints or editing existing ones using the update-endpoint API, and the specific endpoint exceeds the maximum number of 15 endpoint addresses.

  • This limit is currently a hard limit with the service. It can't be increased. For more information, see Endpoint quotas.

BadRequestException when calling the UpdateEndpointsBatch or UpdateEndpoints operation: Too many custom attributes

This error occurs when attempting to add more than 250 attributes. Custom attributes can be a maximum of 15 KB per endpoint.

Issue and solution