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 | Morph is fetching the main data type from Epos Now | Usually just wait for the next stage |
Fetching related data for filters | Morph is fetching linked data needed to evaluate your filters | Usually just wait for the next stage |
Related data fetch for filters completed | Morph 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 Morph created the action jobs | Wait for the run to complete |
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 morph | The morph was missing update actions | Review the Actions setup |
No actions performed for app run id ... | The run completed without applying any updates or deletes, often because nothing matched the filters | Review your filters |
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 Morph 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 Morph 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 Morph queued another attempt | Usually wait and check whether the retry succeeds |
Warning and Failure Messages
| Status Info Example | What It Means | What To Do |
|---|---|---|
Usage limit reached so could not run. X / Y used in billing period | Your usage 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 Morph stopped it | Review the scope of the morph and contact support if this repeats |
Morph 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 ... | Morph could not fetch the main data set | Review the underlying error and try again |
Fetching data for filters failed for <data type> | Morph could not fetch the related data needed for your filters | Review the filter design and any related-data dependencies |
Failed while processing filter data ... | Morph failed before actions started because the filter stage could not be prepared correctly | Review the filter setup and try again |
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 Actions and Usage if the message is plan-limit related.