History and logs
Inspect active Runs, results, and platform failures.
Use these commands to check a Handler's history and results:
wings handler logs <handler-id> --limit 20
wings run show <handler-id> <run-id>
wings usage --days 30
You can also open the Run list in the Console.
Read the status
A Run is recorded as running before the code starts.
It changes to success or error when it ends.
An interrupted Run is marked as error during recovery.
handler logs shows the status, duration, and first error line.
run show also shows error details, the result, and the HTTP status for API and Web responses.
HTTP 200 does not always mean that the Handler succeeded.
See API Trigger responses.
Understand a Wings-side failure
A failure on Wings may include platformFailure.
Its kind is temporary for a temporary failure or limit for a limit being reached.
A stage of before_start means the execution environment had not been called.
With unknown or after_start, an external action may already have happened.
Check the destination before running the job again.
Save the results you need
History has retention limits. Save important results before removing the Handler or other resources.
Keep credentials and personal data out of Handler logs. Do not include private values, raw logs, or user IDs in support messages.