If a Hypersync proof collection fails to complete or the proof does not import successfully, you may see the following timeout error during the process.
Hypersync error
Unable to collect and/or import proof right now. Please try again.
The data for this hypersync could not be collected within 30 minutes. Please edit the hypersync settings to specify a narrower range of data. - TraceId:
Why this happens
Hypersync data processing has a 30-minute time limit. This timeout error most commonly occurs when the dataset being synced is too large to process within that 30-minute window, which is most commonly observed during Jira, AWS, and Zendesk Hypersync proof collections, but can occur with any proof collection Hypersync.
How to fix the issue
To ensure the proof is collected successfully, you’ll need to reduce the size of the dataset being synced.
Follow these steps:
Filter the data into smaller datasets
Apply filters to narrow down the data included in each Hypersync. Using more granular filters can significantly improve processing time.
Create multiple Hypersyncs instead of one large sync
Split the data across multiple Hypersync connections.
For example:One Hypersync for users A–M
A second Hypersync for users N–Z
Re-run the Hypersync proof collections
Once the data is divided into smaller sets, rerun each Hypersync to complete the proof collection and import.
Reducing the dataset size helps ensure each Hypersync completes within the 30-minute processing limit and prevents timeout errors.
If you experience persistent issues, please create a support case by emailing support@hyperproof.io.