## TL;DR

Use pushData from the crawling context, do not open the request queue explicitly when you do not need to, and pass config: Actor.config so everything shares one config. _Source: https://github.com/apify/crawlee/issues/2117 (Crawlee)_

## Steps

1. If Dataset.pushData misbehaves after a Crawlee update, check for duplicate Crawlee installs: multiple copies each create their own global storage config, which is what breaks pushData on the Apify platform. Use pushData from the crawling context, do not open the request queue explicitly when you do not need to, and pass config: Actor.config so everything shares one config.

2. _Source: https://github.com/apify/crawlee/issues/2117 (Crawlee)_

## When to use

Use this skill when you run into "Each and every update to crawlee breaks Dataset.pushData on Apify Platform".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/apify/crawlee/issues/2117
