This topic was automatically generated from Slack. You can find the original thread here.
why is the same workflow executed on different accounts behaves differently. One account runs perfectly. The other account it runs out of memory unless I raise the setting to 512mb
There could be several reasons why the same workflow behaves differently on different accounts, particularly regarding memory usage: 1. Account Settings: Ensure that the memory settings for the workflow are identical on both accounts. You mentioned needing to raise the memory to 512MB on one account, which suggests that the default memory settings might differ between accounts. 2. Environment Differences: Check if there are any environment variables or configurations that differ between the accounts. These could affect how the workflow executes. 3. Data Volume: The data being processed by the workflow might differ between accounts, leading to different memory usage. Ensure that the input data is similar in size and complexity. 4. Workflow Changes: Verify that the workflow code and any dependencies are identical on both accounts. Even small differences in code or library versions can impact memory usage. 5. Pipedream Account Limits: Different accounts might have different limits or configurations set by Pipedream, especially if they are on different pricing plans. If you’ve checked these factors and the issue persists, consider reaching out to Pipedream support for further assistance. You can visit Support - Pipedream for more support options.
This does not offer a solution. As described previously, I took the same file and tested on two different account the memory usage was set to 256 on both. One runs out of memory and one processes the information without any issues. The only way I was able to correct this is to raise memory on the problematic account to 512. Remember, all parameters are identical otherwise.