Status Info Reference
This page explains the most common Status Info messages you may see in the Runs page.
The exact text can sometimes include a data type name, a retry time, or the underlying API error returned by Epos Now.
Fetch and Setup Messages
| Status Info Example | What It Means | What To Do |
|---|---|---|
<data type> is being fetched | Flow is fetching the main data type from Epos Now | Usually just wait for the next stage |
Fetching related data for filters | Flow is fetching linked data needed to evaluate your filters | Usually just wait for the next stage |
Related data fetch for filters completed | Flow finished fetching linked data for filter checks | Wait for the run to continue |
<data type> has been fetched and filtered, actions created | Fetching and filtering finished and Flow created the action jobs | Wait for the run to complete |
Connection established and FTP upload in progress | The export file has been created and Flow has started the FTP or SFTP upload stage | Wait for the final upload result |
Success and No-Action Messages
| Status Info Example | What It Means | What To Do |
|---|---|---|
All actions completed successfully | The run finished normally | No action needed |
No actions defined in flow | The flow was missing update actions or export fields | Review the Actions or Fields setup |
No actions performed for app run id ... | The run completed without any output to deliver, often because nothing matched or empty-result delivery was suppressed | Review your filters and export settings |
Automatic Retry Messages
| Status Info Example | What It Means | What To Do |
|---|---|---|
EN API limit reached. Automatic retry at ... | Epos Now API limits were reached and Flow scheduled another attempt | Usually wait. If this happens often, reduce run frequency or review scope |
API quota exceeded. Automatic retry at ... | Epos Now quota limits were reached and Flow scheduled another attempt | Usually wait. If this happens often, review run volume and timing |
Request time out. Automatic retry at ... | A request timed out and Flow queued another attempt | Usually wait and check whether the retry succeeds |
Warning and Failure Messages
| Status Info Example | What It Means | What To Do |
|---|---|---|
Task limit reached so could not run. X / Y tasks used in billing period | Your task allowance has been exhausted for the current billing period | Wait for reset or upgrade your plan |
App run failed as it exceeded the max run time of X hours | The run took too long and Flow stopped it | Review the scope of the flow and contact support if this repeats |
Flow completed with warning. | The run finished, but one or more jobs failed or warned | Check the logs and review the related failure details |
Failed while fetching primary data ... | Flow could not fetch the main data set | Review the underlying error and try again |
Fetching data for filters failed for <data type> | Flow could not fetch the related data needed for your filters | Review the filter design and any related-data dependencies |
Failed while processing filter data ... | Flow failed before actions started because the filter stage could not be prepared correctly | Review the filter setup and try again |
Failed during zip File | Flow could not complete the zip stage for the export output | Review the export settings and rerun if needed |
Failed to upload file(s). | FTP or SFTP delivery failed | Check the connection, folder path, and overwrite settings |
How To Investigate Further
- Start on Runs to see the overall run state and the full status info text.
- Open Logs when you need record-level detail.
- Check Tasks and Usage if the message is task-limit related.
- Check FTP Connections or Export Data if the message is file-delivery related.