[Bug] HTTP 500 Internal Server Error when publishing plugin via API (GitHub Actions)

murathany

Hello Windy Team,

I am the developer behind a private plugin called Transmission Line Risk Analysis Assistant (windy-plugin-transmission-risk). It is an advanced meteorological risk analysis tool for electrical power grids, calculating ice load, wind, and flashover risks based on CIGRE standards.

Until recently, my GitHub Actions deployment workflow (publish-plugin) was working perfectly. However, while trying to push my latest updates (v1.0.5 / v1.0.6), the deployment started failing consistently with an HTTP 500 error from the Windy API.

The Error Log from GitHub Actions:

--- WINDY API RESPONSE ---
We are sorry, but something broke.
HTTP_STATUS:500
--------------------------
ERROR: Upload failed with status 500
Error: Process completed with exit code 1

Troubleshooting steps I've already taken:

Version Bumping: I suspected the v1.0.5 payload might have gotten stuck or corrupted in the database during the first failed upload, so I bumped the version to v1.0.6 and triggered a fresh build. The exact same 500 error occurred.
Local Build Checks: My local builds (npm run build) and quality gates are completely green. The .tar package is being generated correctly.
API Key Verification: I verified that the WINDY_API_KEY is intact and correct.

My Suspicions / Questions:

Bundle Size Limit? Because this tool performs heavy engineering calculations and generates PDF reports/advanced charts, it relies on libraries like jspdf and chart.js. As a result, my compiled plugin.js bundle size is around 2.7 MB. Did you recently introduce a strict file size limit on the API endpoint that causes the server to drop the connection and throw a 500 error instead of a 4xx validation error?
Temporary Outage? Is there a known issue or maintenance happening with node.windy.com regarding the plugin upload endpoints?

Could someone from the team please take a look or provide some guidance on what might be causing this block?

Thank you for your time and for the great platform!

Best regards,
Murathan Yeniceli
Electrical and Electronics Engineer | Developer

Suty

@murathany Hello, could you please try it once again? We had some issues on our end yesterday and colleagues fixed it already.

murathany

@Suty The problem has been solved, thank you.