Why an AI action cannot run
When an AI action will not start, first compare the displayed cost of that action with the balances and limits currently available on the signed-in account. A blocked request does not always mean the AI service itself is unavailable.
Check the displayed cost and balances
- Note the AI Credit cost shown for the action.
- Open Settings → Credits.
- Check the remaining daily AI allowance.
- Check the remaining monthly AI allowance.
- Check whether applicable Platform Credit fallback is available.
- Return to the action and confirm the same cost is still displayed before retrying.
Included AI Credits are used before applicable Platform Credits according to the current credit rules.
Daily and monthly limits are separate
A request can be blocked because the daily included allowance is exhausted even when some monthly allowance remains.
The reset information shown in the signed-in account is authoritative. Wait for the displayed reset rather than estimating when the daily allowance should return.
If the monthly allowance is exhausted, the available next step depends on the current account balances and whether Platform Credit fallback applies to that action.
Confirm the action has the required data
An AI action can also require eligible input before credits are relevant.
For example, an AI Trade Intelligence review needs eligible completed-trade evidence for the selected instrument and period. AI Playbook Builder needs a valid request that can be mapped into supported Playbook logic.
Read the message shown by the feature before treating every failed request as a credit problem.
If the request appears temporarily unavailable
Refresh the feature once and retry only after confirming the original request did not complete.
Avoid sending the same paid AI request repeatedly while a previous attempt is still loading or synchronizing.
Credits were deducted but no result appeared
Do not repeatedly rerun the same request.
- refresh the feature once;
- check whether the result was saved or appears in the relevant history/report area;
- review Credit Activity when available;
- note the action type, instrument or Playbook, approximate time, displayed cost, and visible error;
- open a Support Ticket if no result exists and the deduction remains.
Providing those details lets Support investigate the specific request without creating additional charges through repeated attempts.
What not to send
A Support Ticket does not need card credentials, wallet private keys, seed phrases, or other payment secrets. Include only the non-sensitive transaction or activity reference visible in TensorAlgo when one is available.