# Scrapy Cloud job logs

The **Log** tab of a [job](index.md#jobs) contains all the messages logged by the
job.

It includes all messages logged with Python’s [`logging`](https://docs.python.org/3/library/logging.html#module-logging), both those from
[Scrapy](https://docs.scrapy.org/en/latest/index.html) built-in components and [your own code](https://docs.scrapy.org/en/latest/topics/logging.html#topics-logging-from-spiders).

## Troubleshooting

Here you can find some help to figure out the meaning of common log messages.

### Ignoring response

> [scrapy.spidermiddlewares.httperror] Ignoring response <403 [https://example.com](https://example.com)>: HTTP status code is not handled or not allowed

By default, after redirects have been followed and retries exceeded, Scrapy
ignores responses with an HTTP status code outside the 200-299 range.

Some HTTP status codes, such as 401, 403 or 429, may be the result of a
[ban](../../../zyte-api/usage/errors.md#zapi-bans). Consider using [Zyte API](../../../zyte-api/get-started.md#zyte-api) to avoid
bans.

If you want to handle those responses in your request callback, instead of
ignoring them:

- Set [`handle_httpstatus_all`](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#std-reqmeta-handle_httpstatus_all) or [`handle_httpstatus_list`](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#std-reqmeta-handle_httpstatus_list)
  in your request metadata to handle such responses for a specific request:
  ```python
  Request("https://example.com", meta={"handle_httpstatus_list": {403}})
  ```
- Use the [`HTTPERROR_ALLOW_ALL`](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#std-setting-HTTPERROR_ALLOW_ALL) or
  [`HTTPERROR_ALLOWED_CODES`](https://docs.scrapy.org/en/latest/topics/spider-middleware.html#std-setting-HTTPERROR_ALLOWED_CODES) settings to handle such responses for
  all requests.
