# What should I do when a command times out?

Canonical URL: https://help.iagenify.com/faqs/tools/what-should-i-do-when-a-command-times-out

[← Back to Tools FAQs](https://help.iagenify.com/faqs/tools)

HELP CENTER · FAQ Tools 1 min read
# What should I do when a command times out?
A timeout means the tool stopped waiting at its limit; it does not prove the command stopped or that its work failed. Check whether the process is still running and inspect side effects before launching the same command again.
IaGenify
Tools

## Determine what happened to the process
Look for a process or job identifier, session handle, or log entry that shows whether execution continues. If the tool provides a live session, poll that session rather than starting a duplicate that may perform overlapping writes.
Inspect outputs that may have been created before the timeout, such as partial files, database rows, deployments, or sent messages. Compare timestamps and completion markers with the intended scope before deciding what remains.
## Retry with a safer plan
If the process ended without completing, determine whether the command is idempotent. For non-idempotent work, use a unique operation key or reconcile existing results first; resume from a checkpoint when supported.
If timeouts repeat, reduce input size or divide work into observable stages and capture progress logs. Do not raise the limit indefinitely: long waits can hide a stalled process, while checkpointed tasks make recovery clearer. [← Back to Tools FAQs](https://help.iagenify.com/faqs/tools)