Skip to content

Unexpected 500s #8

@corviday

Description

@corviday

The backend is throwing some unexpected 500s during testing of the front end, especially of watersheds with a species parameter. It's pretty intermittant and hard to reproduce, so it might be something like a timeout or race condition. Everyone's favourite: a bug you can't reproduce!

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions