# Seqera x AWS problem?

**URL:** <https://community.seqera.io/t/seqera-x-aws-problem/2721>\
**Category:** Ask for help\
**Tags:** aws, platform\
**Created:** [July 14, 2026, 9:05am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721 "2026-07-14T09:05:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheoG](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/theog/32/2481_2.png) [@TheoG](https://community.seqera.io/u/TheoG)\
**Post date:** [July 14, 2026, 9:05am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721/1 "2026-07-14T09:05:49Z")

</div>

Hello,

I am encountering problems running pipelines through Seqera platform.  
My runs are stuck as “submitted”, when I check through AWS console, there is no job in any AWS Batch queue.

I just tried running an “hello world” pipeline through the community showcase environment (name confident\_lavoisier / ID 44KMAnm7duNqS0), it seems to have the same problem (stuck as “submitted”, but no progress, logs tab showing “waiting for output log”).

Is there any problem or planned maintenance?

Cheers,

Theo

---

<div class="post-metadata">

**Author:** ![matteofiandesio](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/matteofiandesio/32/71_2.png) [@matteofiandesio](https://community.seqera.io/u/matteofiandesio)\
**Post date:** [July 14, 2026, 9:07am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721/2 "2026-07-14T09:07:48Z")

</div>

Hello @TheoG we are running a database migration on the platform which is taking more than expected to complete. We have a running incident about this and you can follow the process here [https://status.seqera.io/](https://status.seqera.io/). Sorry for the inconvenience

---

<div class="post-metadata">

**Author:** ![TheoG](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/theog/32/2481_2.png) [@TheoG](https://community.seqera.io/u/TheoG)\
**Post date:** [July 14, 2026, 9:13am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721/3 "2026-07-14T09:13:58Z")

</div>

Thanks for the quick update!

For future reference, is there any other channel where we can check for scheduled maintenance?

---

<div class="post-metadata">

**Author:** ![matteofiandesio](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/matteofiandesio/32/71_2.png) [@matteofiandesio](https://community.seqera.io/u/matteofiandesio)\
**Post date:** [July 14, 2026, 9:56am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721/4 "2026-07-14T09:56:22Z")

</div>

@TheoG we usually put standard maintanance in the same link as above or as banners in the platform. For this specific instance it was the weekly production rollout that had a faulty migration: we usually don’t communicate those except in the release notes in the public facing documentation (after the release).

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\
**Post date:** [July 21, 2026, 9:56am UTC](https://community.seqera.io/t/seqera-x-aws-problem/2721/5 "2026-07-21T09:56:40Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.