Realm

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add retry policy to Atlas Trigger

    A failed Atlas trigger gets suspended and will not retry without manual intervention. Some transient conditions can be retried and it would be useful to configure a retry policy with a trigger (at the Realm Function level). Retry X times with Y back-off seconds between retries, then fail (plus notification policy).

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow manually disabled trigger to resume without resume token

    I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply start listening for new events upon restart).

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  3. Notification on function failure

    I would like a notification if a trigger fires a function, and the function fails.

    I have a scheduled trigger that calls a function every day. I have no idea if the function fails unless I manually log in and check the status. I would like to be alerted in the event of a failure. I've gotten around this by manually setting up Slack notifications.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  4. Configure Realm notifications

    Currently only all project owners of the Atlas project in where your Realm app situates will receive notification of suspended trigger. This currently cannot be customized. We want to have the possibility to configure the notifications to include additional emails, not only for project owners.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add the ability to use a value to reference a database in a trigger

    It would be great if we could use values for the database reference in a trigger, instead of having to select a database from a drop-down.

    An actual use case:

    To be able to use Realm for our various staging areas, we have created multiple Realm apps. One for production, one for UAT, one for test, etc. Each of them pointing to the databases for their respective staging environment.

    We are using Github deployments, and we use a separate branch for each of the staging environments. So when something gets committed to the "deploy-test" branch, it gets to be deployed…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  6. Realm Trigger Event Projection should support exclusion

    Realm triggers with a projections must include "operationType": 1. This makes excluding fields impossible because, according to the documentation:

    if you exclude fields, you cannot also specify the inclusion of fields

    The only work around we have found is to list every single field in the database and this would require an update anytime we add another field to the model. This is quite cumbersome and should be easily resolved with a simple exclusion.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  7. Disable/Enable all triggers at once

    It would be very useful to be able to disable/enable all triggers of realm application at once. It useful for instance when you restore data from backup or make some big changes, and it is not needed to run triggers on every change

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  8. changeEvent cluster name

    I want to be able to programmatically access the clusterName from change event or global variable for example:

    changeEvent.ns.cluster = <CLUSTER/SERVICE name>
    global.CLUSTER_NAME

    I need this when I want to perform an update on same collection/document after the trigger, but i don't want to hardcode the clusterName - because i have multiple environments - each has its own cluster (dev/sandbox/prod etc...)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  9. One-time scheduled triggers

    At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  10. Sign in with Apple Server to Server Endpoint

    It would be great if there would be an easier way to set up Apple's server to server notifications to deal with authorisation changes, user deletes etc. That would allow a user to sign out or delete their user through any device without having to login to the app.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  11. more aws eventbridge options

    • Push multiple triggers to 1 Eventbridge eventbus
    • Use the eventbridge SDK from the AWS service (now its not available and i have to use a custom aws sdk import, increasing the trigger time x 10 vs the normal eventbridge connector).
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  12. Logout trigger

    There's a trigger for login, but there isn't one for logout (as far as I can tell). I would like a trigger on logout as well to perform cleanup of any of the side effects from the login trigger.

    This request is really a result of a separate request that is more important (https://feedback.mongodb.com/forums/923521-realm/suggestions/42102031-decode-user-token) but if there was a trigger for both login and logout it would tie me over until then.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base